Re: [patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-19 Thread Matt Fleming
On Mon, 18 Nov, at 10:16:41AM, Dave Young wrote: > Matt, desc_version is already in boot_params.efi_info, so kexec-tools > can get the version from there. I do not need to export it as another > file. OK, cool. > I think for now we do not need worry much about the compatibility > issue, do you

Re: [patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-19 Thread Matt Fleming
On Mon, 18 Nov, at 10:16:41AM, Dave Young wrote: Matt, desc_version is already in boot_params.efi_info, so kexec-tools can get the version from there. I do not need to export it as another file. OK, cool. I think for now we do not need worry much about the compatibility issue, do you think

Re: [patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-17 Thread Dave Young
> > > +/* > > > + * These are default attributes that are added for every memmap entry. > > > + */ > > > +static struct attribute *def_attrs[] = { > > > + _type_attr.attr, > > > + _phys_addr_attr.attr, > > > + _virt_addr_attr.attr, > > > + _num_pages_attr.attr, > > > + _attribute_attr.attr, > > >

Re: [patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-17 Thread Dave Young
+/* + * These are default attributes that are added for every memmap entry. + */ +static struct attribute *def_attrs[] = { + map_type_attr.attr, + map_phys_addr_attr.attr, + map_virt_addr_attr.attr, + map_num_pages_attr.attr, + map_attribute_attr.attr, + NULL +};

Re: [patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-13 Thread Dave Young
On 11/13/13 at 03:50pm, Matt Fleming wrote: > On Tue, 05 Nov, at 04:20:12PM, dyo...@redhat.com wrote: > > kexec kernel will need exactly same mapping for > > efi runtime memory ranges. Thus here export the > > runtime ranges mapping to sysfs, kexec-tools > > will assemble them and pass to 2nd

Re: [patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-13 Thread Matt Fleming
On Tue, 05 Nov, at 04:20:12PM, dyo...@redhat.com wrote: > kexec kernel will need exactly same mapping for > efi runtime memory ranges. Thus here export the > runtime ranges mapping to sysfs, kexec-tools > will assemble them and pass to 2nd kernel via > setup_data. > > Introducing a new directly

Re: [patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-13 Thread Matt Fleming
On Tue, 05 Nov, at 04:20:12PM, dyo...@redhat.com wrote: kexec kernel will need exactly same mapping for efi runtime memory ranges. Thus here export the runtime ranges mapping to sysfs, kexec-tools will assemble them and pass to 2nd kernel via setup_data. Introducing a new directly

Re: [patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-13 Thread Dave Young
On 11/13/13 at 03:50pm, Matt Fleming wrote: On Tue, 05 Nov, at 04:20:12PM, dyo...@redhat.com wrote: kexec kernel will need exactly same mapping for efi runtime memory ranges. Thus here export the runtime ranges mapping to sysfs, kexec-tools will assemble them and pass to 2nd kernel via

[patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-05 Thread dyoung
kexec kernel will need exactly same mapping for efi runtime memory ranges. Thus here export the runtime ranges mapping to sysfs, kexec-tools will assemble them and pass to 2nd kernel via setup_data. Introducing a new directly /sys/firmware/efi/efi-runtime-map Just like /sys/firmware/memmap.

[patch 5/7 v2] export efi runtime memory mapping to sysfs

2013-11-05 Thread dyoung
kexec kernel will need exactly same mapping for efi runtime memory ranges. Thus here export the runtime ranges mapping to sysfs, kexec-tools will assemble them and pass to 2nd kernel via setup_data. Introducing a new directly /sys/firmware/efi/efi-runtime-map Just like /sys/firmware/memmap.