Displaying 9 results from an estimated 9 matches for "label_size".
2010 Jul 14
2
[PATCH] gfxboot: add include and menu include support
...e\n");
if(argc > 2) show_message(argv[2]);
@@ -313,16 +314,24 @@ void chop_line(char *s)
// return:
// 0: ok, 1: error
//
-int read_config_file(void)
+int read_config_file(const char *filename)
{
FILE *f;
char *s, *t, buf[MAX_CONFIG_LINE_LEN];
- unsigned u, menu_idx = 0, label_size = 0, append_size = 0;
- menu_t *menu_ptr = NULL, **menu_next = &menu;
+ unsigned u, top_level = 0;
- menu_default = calloc(1, sizeof *menu_default);
+ if(!strcmp(filename, "~")) {
+ top_level = 1;
+ filename = syslinux_config_file();
+ gfx_menu.entries = 0;
+ gfx_men...
2010 Apr 09
2
[PATCH] gfxboot: support MENU LABEL statement
..."timeout")) {
+ if(!strcasecmp(s, "timeout")) {
timeout = atoi(t);
continue;
}
- if(!strcmp(s, "default")) {
+ if(!strcasecmp(s, "default")) {
menu_default->label = strdup(t);
u = strlen(t);
if(u > label_size) label_size = u;
continue;
}
- if(!strcmp(s, "label")) {
+ if(!strcasecmp(s, "label")) {
menu_ptr = *menu_next = calloc(1, sizeof **menu_next);
menu_next = &menu_ptr->next;
menu_idx++;
@@ -343,37 +343,51 @@ int read_config_file...
2020 Sep 10
2
Re: Two questions about NVDIMM devices
...the ball on docs.
I still can't see it in the documentation, would it be possible to be
clear about 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 impor...
2020 Sep 10
2
Re: Two questions about NVDIMM devices
...le to be
>>>> clear about 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...
2020 Sep 10
2
Re: Two questions about NVDIMM devices
...in the documentation, would it be possible to be
>> clear about 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 requ...
2020 Sep 10
0
Re: Two questions about NVDIMM devices
...ll can't see it in the documentation, would it be possible to be
> clear about 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
>...
2020 Sep 14
0
Re: Two questions about NVDIMM devices
...bout 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...
2020 Sep 10
0
Re: Two questions about NVDIMM devices
...ld it be possible to be
> >> clear about 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...
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