Displaying 20 results from an estimated 23 matches for "align_up".
Did you mean:
_align_up
2020 Sep 10
2
Re: Two questions about NVDIMM devices
...it in the docs, please? For first, it's not very intuitive
to figure out that (if I've figured out it correctly) on POWER one
*must* specify the NVDIMM size S as
S == aligned_size + label_size
and that size is used for the QEMU device; while on x86_64 one can
specify any size S and
align_up(S)
will be used for the QEMU device (and label size doesn't influence the
value). And additional alignment may be required for having any memory
hot plug working.
For second, and more importantly, I'm afraid that without documenting
it, future changes may break the current behavior witho...
2010 Sep 23
3
[PATCH 1/1] Rename camel case variables in channel.c (updated)
...Flags)
+int VmbusChannelSendPacket(struct vmbus_channel *channel, const void *buffer,
+ u32 bufferlen, u64 requestid,
+ enum vmbus_packet_type type, u32 flags)
{
struct vmpacket_descriptor desc;
- u32 packetLen = sizeof(struct vmpacket_descriptor) + BufferLen;
- u32 packetLenAligned = ALIGN_UP(packetLen, sizeof(u64));
- struct scatterlist bufferList[3];
- u64 alignedData = 0;
+ u32 packetlen = sizeof(struct vmpacket_descriptor) + bufferlen;
+ u32 packetlen_aligned = ALIGN_UP(packetlen, sizeof(u64));
+ struct scatterlist bufferlist[3];
+ u64 aligned_data = 0;
int ret;
DPRINT_DBG(VMB...
2010 Sep 23
3
[PATCH 1/1] Rename camel case variables in channel.c (updated)
...Flags)
+int VmbusChannelSendPacket(struct vmbus_channel *channel, const void *buffer,
+ u32 bufferlen, u64 requestid,
+ enum vmbus_packet_type type, u32 flags)
{
struct vmpacket_descriptor desc;
- u32 packetLen = sizeof(struct vmpacket_descriptor) + BufferLen;
- u32 packetLenAligned = ALIGN_UP(packetLen, sizeof(u64));
- struct scatterlist bufferList[3];
- u64 alignedData = 0;
+ u32 packetlen = sizeof(struct vmpacket_descriptor) + bufferlen;
+ u32 packetlen_aligned = ALIGN_UP(packetlen, sizeof(u64));
+ struct scatterlist bufferlist[3];
+ u64 aligned_data = 0;
int ret;
DPRINT_DBG(VMB...
2010 Sep 30
2
[PATCH 1/1] staging: hv: Remove camel case variables in channel.c
...Flags)
+int VmbusChannelSendPacket(struct vmbus_channel *channel, const void *buffer,
+ u32 bufferlen, u64 requestid,
+ enum vmbus_packet_type type, u32 flags)
{
struct vmpacket_descriptor desc;
- u32 packetLen = sizeof(struct vmpacket_descriptor) + BufferLen;
- u32 packetLenAligned = ALIGN_UP(packetLen, sizeof(u64));
- struct scatterlist bufferList[3];
- u64 alignedData = 0;
+ u32 packetlen = sizeof(struct vmpacket_descriptor) + bufferlen;
+ u32 packetlen_aligned = ALIGN_UP(packetlen, sizeof(u64));
+ struct scatterlist bufferlist[3];
+ u64 aligned_data = 0;
int ret;
DPRINT_DBG(VMB...
2010 Sep 30
2
[PATCH 1/1] staging: hv: Remove camel case variables in channel.c
...Flags)
+int VmbusChannelSendPacket(struct vmbus_channel *channel, const void *buffer,
+ u32 bufferlen, u64 requestid,
+ enum vmbus_packet_type type, u32 flags)
{
struct vmpacket_descriptor desc;
- u32 packetLen = sizeof(struct vmpacket_descriptor) + BufferLen;
- u32 packetLenAligned = ALIGN_UP(packetLen, sizeof(u64));
- struct scatterlist bufferList[3];
- u64 alignedData = 0;
+ u32 packetlen = sizeof(struct vmpacket_descriptor) + bufferlen;
+ u32 packetlen_aligned = ALIGN_UP(packetlen, sizeof(u64));
+ struct scatterlist bufferlist[3];
+ u64 aligned_data = 0;
int ret;
DPRINT_DBG(VMB...
2020 Sep 10
2
Re: Two questions about NVDIMM devices
...>>>> *must* specify the NVDIMM size S as
>>>>
>>>> S == aligned_size + label_size
>>>>
>>>> and that size is used for the QEMU device; while on x86_64 one can
>>>> specify any size S and
>>>>
>>>> align_up(S)
>>>>
>>>> will be used for the QEMU device (and label size doesn't influence the
>>>> value). And additional alignment may be required for having any memory
>>>> hot plug working.
>>>>
>>>> For second, and more importan...
2010 Sep 23
1
[PATCH 1/1] Rename camel case variables in channel.c
...Flags)
+int VmbusChannelSendPacket(struct vmbus_channel *channel, const void *buffer,
+ u32 bufferlen, u64 requestid,
+ enum vmbus_packet_type type, u32 flags)
{
struct vmpacket_descriptor desc;
- u32 packetLen = sizeof(struct vmpacket_descriptor) + BufferLen;
- u32 packetLenAligned = ALIGN_UP(packetLen, sizeof(u64));
- struct scatterlist bufferList[3];
- u64 alignedData = 0;
+ u32 packetlen = sizeof(struct vmpacket_descriptor) + bufferlen;
+ u32 packetlen_aligned = ALIGN_UP(packetlen, sizeof(u64));
+ struct scatterlist bufferlist[3];
+ u64 aligned_data = 0;
int ret;
DPRINT_DBG(VMB...
2010 Sep 23
1
[PATCH 1/1] Rename camel case variables in channel.c
...Flags)
+int VmbusChannelSendPacket(struct vmbus_channel *channel, const void *buffer,
+ u32 bufferlen, u64 requestid,
+ enum vmbus_packet_type type, u32 flags)
{
struct vmpacket_descriptor desc;
- u32 packetLen = sizeof(struct vmpacket_descriptor) + BufferLen;
- u32 packetLenAligned = ALIGN_UP(packetLen, sizeof(u64));
- struct scatterlist bufferList[3];
- u64 alignedData = 0;
+ u32 packetlen = sizeof(struct vmpacket_descriptor) + bufferlen;
+ u32 packetlen_aligned = ALIGN_UP(packetlen, sizeof(u64));
+ struct scatterlist bufferlist[3];
+ u64 aligned_data = 0;
int ret;
DPRINT_DBG(VMB...
2020 Sep 10
2
Re: Two questions about NVDIMM devices
...re out that (if I've figured out it correctly) on POWER one
>> *must* specify the NVDIMM size S as
>>
>> S == aligned_size + label_size
>>
>> and that size is used for the QEMU device; while on x86_64 one can
>> specify any size S and
>>
>> align_up(S)
>>
>> will be used for the QEMU device (and label size doesn't influence the
>> value). And additional alignment may be required for having any memory
>> hot plug working.
>>
>> For second, and more importantly, I'm afraid that without documenting
&...
2020 Sep 10
0
Re: Two questions about NVDIMM devices
...not very intuitive
> to figure out that (if I've figured out it correctly) on POWER one
> *must* specify the NVDIMM size S as
>
> S == aligned_size + label_size
>
> and that size is used for the QEMU device; while on x86_64 one can
> specify any size S and
>
> align_up(S)
>
> will be used for the QEMU device (and label size doesn't influence the
> value). And additional alignment may be required for having any memory
> hot plug working.
>
> For second, and more importantly, I'm afraid that without documenting
> it, future changes m...
2010 Sep 20
1
[PATCH 2/2] staging: hv: Remove camel cases from vmbus channel functions
...const void *buffer,
+ u32 bufferlen, u64 requestid,
+ enum vmbus_packet_type type, u32 flags)
{
struct vmpacket_descriptor desc;
- u32 packetLen = sizeof(struct vmpacket_descriptor) + BufferLen;
+ u32 packetLen = sizeof(struct vmpacket_descriptor) + bufferlen;
u32 packetLenAligned = ALIGN_UP(packetLen, sizeof(u64));
struct scatterlist bufferList[3];
u64 alignedData = 0;
int ret;
DPRINT_DBG(VMBUS, "channel %p buffer %p len %d",
- Channel, Buffer, BufferLen);
+ channel, buffer, bufferlen);
- DumpVmbusChannel(Channel);
+ dumpvmbuschannel(channel);
/* ASSE...
2010 Sep 20
1
[PATCH 2/2] staging: hv: Remove camel cases from vmbus channel functions
...const void *buffer,
+ u32 bufferlen, u64 requestid,
+ enum vmbus_packet_type type, u32 flags)
{
struct vmpacket_descriptor desc;
- u32 packetLen = sizeof(struct vmpacket_descriptor) + BufferLen;
+ u32 packetLen = sizeof(struct vmpacket_descriptor) + bufferlen;
u32 packetLenAligned = ALIGN_UP(packetLen, sizeof(u64));
struct scatterlist bufferList[3];
u64 alignedData = 0;
int ret;
DPRINT_DBG(VMBUS, "channel %p buffer %p len %d",
- Channel, Buffer, BufferLen);
+ channel, buffer, bufferlen);
- DumpVmbusChannel(Channel);
+ dumpvmbuschannel(channel);
/* ASSE...
2020 Sep 14
0
Re: Two questions about NVDIMM devices
...> > > >
> > > > > S == aligned_size + label_size
> > > > >
> > > > > and that size is used for the QEMU device; while on x86_64 one can
> > > > > specify any size S and
> > > > >
> > > > > align_up(S)
> > > > >
> > > > > will be used for the QEMU device (and label size doesn't influence the
> > > > > value). And additional alignment may be required for having any memory
> > > > > hot plug working.
The ppc64-specific requiremen...
2020 Sep 10
0
Re: Two questions about NVDIMM devices
...correctly) on POWER one
> >> *must* specify the NVDIMM size S as
> >>
> >> S == aligned_size + label_size
> >>
> >> and that size is used for the QEMU device; while on x86_64 one can
> >> specify any size S and
> >>
> >> align_up(S)
> >>
> >> will be used for the QEMU device (and label size doesn't influence the
> >> value). And additional alignment may be required for having any memory
> >> hot plug working.
> >>
> >> For second, and more importantly, I'm afr...
2020 Jun 18
1
[PATCH] Kbuild for klibc and nfsmount: fix multiple definitions
...ibc/sbrk.c
+++ b/usr/klibc/sbrk.c
@@ -11,7 +11,7 @@
#if !_KLIBC_NO_MMU /* uClinux doesn't have brk() */
-char *__current_brk; /* Common with brk.c */
+extern char *__current_brk; /* Common with brk.c */
/* p is an address, a is alignment; must be a power of 2 */
static inline void *align_up(void *p, uintptr_t a)
diff --git a/usr/klibc/srand48.c b/usr/klibc/srand48.c
index e1c95672f731..dd2112764af8 100644
--- a/usr/klibc/srand48.c
+++ b/usr/klibc/srand48.c
@@ -5,7 +5,7 @@
#include <stdlib.h>
#include <stdint.h>
-unsigned short __rand48_seed[3]; /* Common with mrand48.c...
2010 Dec 06
7
[PATCH 1/8] staging: hv: Convert camel case struct fields in vstorage.h to lowercase
From: Hank Janssen <hjanssen at microsoft.com>
Convert camel case struct fields in vstorage.h to lowercase
Signed-off-by: Abhishek Kane <v-abkane at microsoft.com>
Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com>
Signed-off-by: Hank Janssen <hjanssen at microsoft.com>
---
drivers/staging/hv/storvsc.c | 133 +++++++++++++++++++++--------------------
2010 Dec 06
7
[PATCH 1/8] staging: hv: Convert camel case struct fields in vstorage.h to lowercase
From: Hank Janssen <hjanssen at microsoft.com>
Convert camel case struct fields in vstorage.h to lowercase
Signed-off-by: Abhishek Kane <v-abkane at microsoft.com>
Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com>
Signed-off-by: Hank Janssen <hjanssen at microsoft.com>
---
drivers/staging/hv/storvsc.c | 133 +++++++++++++++++++++--------------------
2020 Jul 02
3
Two questions about NVDIMM devices
Hi,
I've met two situations with NVDIMM support in libvirt where I'm not
sure all the parties (libvirt & I) do the things correctly.
The first problem is with memory alignment and size changes. In
addition to the size changes applied to NVDIMMs by QEMU, libvirt also
makes some NVDIMM size changes for better alignments, in
qemuDomainMemoryDeviceAlignSize. This can lead to the size
2010 Nov 01
5
[PATCH 03/10] staging: hv: Convert camel cased struct fields in hv.h to lower cases
...nal_event_buffer =
kmalloc(sizeof(struct hv_input_signal_event_buffer),
GFP_KERNEL);
- if (!gHvContext.SignalEventBuffer)
+ if (!g_hv_context.signal_event_buffer)
goto Cleanup;
- gHvContext.SignalEventParam =
+ g_hv_context.signal_event_param =
(struct hv_input_signal_event *)
- (ALIGN_UP((unsigned long)gHvContext.SignalEventBuffer,
+ (ALIGN_UP((unsigned long)
+ g_hv_context.signal_event_buffer,
HV_HYPERCALL_PARAM_ALIGN));
- gHvContext.SignalEventParam->connectionid.asu32 = 0;
- gHvContext.SignalEventParam->connectionid.u.id =
+ g_hv_context.signal_event_param-&g...
2010 Nov 01
5
[PATCH 03/10] staging: hv: Convert camel cased struct fields in hv.h to lower cases
...nal_event_buffer =
kmalloc(sizeof(struct hv_input_signal_event_buffer),
GFP_KERNEL);
- if (!gHvContext.SignalEventBuffer)
+ if (!g_hv_context.signal_event_buffer)
goto Cleanup;
- gHvContext.SignalEventParam =
+ g_hv_context.signal_event_param =
(struct hv_input_signal_event *)
- (ALIGN_UP((unsigned long)gHvContext.SignalEventBuffer,
+ (ALIGN_UP((unsigned long)
+ g_hv_context.signal_event_buffer,
HV_HYPERCALL_PARAM_ALIGN));
- gHvContext.SignalEventParam->connectionid.asu32 = 0;
- gHvContext.SignalEventParam->connectionid.u.id =
+ g_hv_context.signal_event_param-&g...