On 12/17/13 at 04:58pm, Borislav Petkov wrote:
> On Tue, Dec 17, 2013 at 02:34:36PM +0800, Dave Young wrote:
> > They are moved to efi.c efi_setup_init(), I'm not sure if I expained
> > clear enough, in current code parse_efi_setup only accept one argument
> > phys_addr so I will mapping it with
On Tue, Dec 17, 2013 at 02:34:36PM +0800, Dave Young wrote:
> They are moved to efi.c efi_setup_init(), I'm not sure if I expained
> clear enough, in current code parse_efi_setup only accept one argument
> phys_addr so I will mapping it with sizeof(struct setup_data) to
> get the payload size then
On Tue, Dec 17, 2013 at 02:34:36PM +0800, Dave Young wrote:
They are moved to efi.c efi_setup_init(), I'm not sure if I expained
clear enough, in current code parse_efi_setup only accept one argument
phys_addr so I will mapping it with sizeof(struct setup_data) to
get the payload size then get
On 12/17/13 at 04:58pm, Borislav Petkov wrote:
On Tue, Dec 17, 2013 at 02:34:36PM +0800, Dave Young wrote:
They are moved to efi.c efi_setup_init(), I'm not sure if I expained
clear enough, in current code parse_efi_setup only accept one argument
phys_addr so I will mapping it with
On 12/16/13 at 12:33pm, Borislav Petkov wrote:
> On Mon, Dec 16, 2013 at 10:00:10AM +0800, Dave Young wrote:
> > > > - print_efi_memmap();
> > > > + if (efi_setup) {
> > > > + int s;
> > > > + struct efi_setup_data *data;
> > > > +
> > > > + s
On Mon, Dec 16, 2013 at 10:00:10AM +0800, Dave Young wrote:
> > > - print_efi_memmap();
> > > + if (efi_setup) {
> > > + int s;
> > > + struct efi_setup_data *data;
> > > +
> > > + s = sizeof(*data) + nr_efi_runtime_map * sizeof(data->map[0]);
> > > + data =
On Mon, Dec 16, 2013 at 10:00:10AM +0800, Dave Young wrote:
- print_efi_memmap();
+ if (efi_setup) {
+ int s;
+ struct efi_setup_data *data;
+
+ s = sizeof(*data) + nr_efi_runtime_map * sizeof(data-map[0]);
+ data = early_memremap(efi_setup, s);
On 12/16/13 at 12:33pm, Borislav Petkov wrote:
On Mon, Dec 16, 2013 at 10:00:10AM +0800, Dave Young wrote:
- print_efi_memmap();
+ if (efi_setup) {
+ int s;
+ struct efi_setup_data *data;
+
+ s = sizeof(*data) +
> > - print_efi_memmap();
> > + if (efi_setup) {
> > + int s;
> > + struct efi_setup_data *data;
> > +
> > + s = sizeof(*data) + nr_efi_runtime_map * sizeof(data->map[0]);
> > + data = early_memremap(efi_setup, s);
> > + if (!data)
> > +
- print_efi_memmap();
+ if (efi_setup) {
+ int s;
+ struct efi_setup_data *data;
+
+ s = sizeof(*data) + nr_efi_runtime_map * sizeof(data-map[0]);
+ data = early_memremap(efi_setup, s);
+ if (!data)
+ return;
On Mon, Dec 09, 2013 at 05:42:23PM +0800, Dave Young wrote:
> For kexec/kdump kernel efi runtime mappings are saved, printing original whole
> memmap ranges does not make sense anymore. So introduce a new function to only
> print runtime maps in case kexec/kdump kernel is used.
>
> changelog:
>
On Mon, Dec 09, 2013 at 05:42:23PM +0800, Dave Young wrote:
For kexec/kdump kernel efi runtime mappings are saved, printing original whole
memmap ranges does not make sense anymore. So introduce a new function to only
print runtime maps in case kexec/kdump kernel is used.
changelog:
Matt:
For kexec/kdump kernel efi runtime mappings are saved, printing original whole
memmap ranges does not make sense anymore. So introduce a new function to only
print runtime maps in case kexec/kdump kernel is used.
changelog:
Matt: use efi_setup instead of esdata
share function
For kexec/kdump kernel efi runtime mappings are saved, printing original whole
memmap ranges does not make sense anymore. So introduce a new function to only
print runtime maps in case kexec/kdump kernel is used.
changelog:
Matt: use efi_setup instead of esdata
share function
14 matches
Mail list logo
