Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

On Tue, Jan 21, 2020 at 11:17:19AM -0600, Eric W. Biederman wrote: > Andy Shevchenko writes: > > On Tue, Jan 21, 2020 at 12:18:03AM +0100, Ard Biesheuvel wrote: > >> On Mon, 20 Jan 2020 at 23:31, Andy Shevchenko > >> wrote: > >> > On Mon, Jan 20, 2020 at 9:28 PM Eric W. Biederman > >> >

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

Ccing efi people. On 12/16/16 at 02:33pm, Jean Delvare wrote: > On Fri, 16 Dec 2016 14:18:58 +0200, Andy Shevchenko wrote: > > On Fri, 2016-12-16 at 10:32 +0800, Dave Young wrote: > > > On 12/15/16 at 12:28pm, Jean Delvare wrote: > > > > I am no kexec expert but this confuses me. Shouldn't the

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

Ccing efi people. On 12/16/16 at 02:33pm, Jean Delvare wrote: > On Fri, 16 Dec 2016 14:18:58 +0200, Andy Shevchenko wrote: > > On Fri, 2016-12-16 at 10:32 +0800, Dave Young wrote: > > > On 12/15/16 at 12:28pm, Jean Delvare wrote: > > > > I am no kexec expert but this confuses me. Shouldn't the

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

On 12/16/16 at 02:18pm, Andy Shevchenko wrote: > On Fri, 2016-12-16 at 10:32 +0800, Dave Young wrote: > > On 12/15/16 at 12:28pm, Jean Delvare wrote: > > > Hi Andy, > > > > > > On Fri,  2 Dec 2016 21:54:16 +0200, Andy Shevchenko wrote: > > > > Until now kexec'ed kernel has no clue where to look

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

On 12/16/16 at 02:18pm, Andy Shevchenko wrote: > On Fri, 2016-12-16 at 10:32 +0800, Dave Young wrote: > > On 12/15/16 at 12:28pm, Jean Delvare wrote: > > > Hi Andy, > > > > > > On Fri,  2 Dec 2016 21:54:16 +0200, Andy Shevchenko wrote: > > > > Until now kexec'ed kernel has no clue where to look

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

On Fri, 16 Dec 2016 14:18:58 +0200, Andy Shevchenko wrote: > On Fri, 2016-12-16 at 10:32 +0800, Dave Young wrote: > > On 12/15/16 at 12:28pm, Jean Delvare wrote: > > > I am no kexec expert but this confuses me. Shouldn't the second > > > kernel have access to the EFI systab as the first kernel

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

On Fri, 16 Dec 2016 14:18:58 +0200, Andy Shevchenko wrote: > On Fri, 2016-12-16 at 10:32 +0800, Dave Young wrote: > > On 12/15/16 at 12:28pm, Jean Delvare wrote: > > > I am no kexec expert but this confuses me. Shouldn't the second > > > kernel have access to the EFI systab as the first kernel

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

On Fri, 2016-12-16 at 10:32 +0800, Dave Young wrote: > On 12/15/16 at 12:28pm, Jean Delvare wrote: > > Hi Andy, > > > > On Fri,  2 Dec 2016 21:54:16 +0200, Andy Shevchenko wrote: > > > Until now kexec'ed kernel has no clue where to look for DMI entry > > > point. > > > > > > Pass it via kernel

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

On Fri, 2016-12-16 at 10:32 +0800, Dave Young wrote: > On 12/15/16 at 12:28pm, Jean Delvare wrote: > > Hi Andy, > > > > On Fri,  2 Dec 2016 21:54:16 +0200, Andy Shevchenko wrote: > > > Until now kexec'ed kernel has no clue where to look for DMI entry > > > point. > > > > > > Pass it via kernel

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

On 12/15/16 at 12:28pm, Jean Delvare wrote: > Hi Andy, > > On Fri, 2 Dec 2016 21:54:16 +0200, Andy Shevchenko wrote: > > Until now kexec'ed kernel has no clue where to look for DMI entry point. > > > > Pass it via kernel command line parameter in the same way as it's done for > > ACPI > >

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

On 12/15/16 at 12:28pm, Jean Delvare wrote: > Hi Andy, > > On Fri, 2 Dec 2016 21:54:16 +0200, Andy Shevchenko wrote: > > Until now kexec'ed kernel has no clue where to look for DMI entry point. > > > > Pass it via kernel command line parameter in the same way as it's done for > > ACPI > >

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

Hi Andy, On Fri, 2 Dec 2016 21:54:16 +0200, Andy Shevchenko wrote: > Until now kexec'ed kernel has no clue where to look for DMI entry point. > > Pass it via kernel command line parameter in the same way as it's done for > ACPI > RSDP. I am no kexec expert but this confuses me. Shouldn't the

Re: [PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

Hi Andy, On Fri, 2 Dec 2016 21:54:16 +0200, Andy Shevchenko wrote: > Until now kexec'ed kernel has no clue where to look for DMI entry point. > > Pass it via kernel command line parameter in the same way as it's done for > ACPI > RSDP. I am no kexec expert but this confuses me. Shouldn't the

[PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

Until now kexec'ed kernel has no clue where to look for DMI entry point. Pass it via kernel command line parameter in the same way as it's done for ACPI RSDP. Signed-off-by: Andy Shevchenko --- Documentation/admin-guide/kernel-parameters.txt | 5 +

[PATCH v1 2/2] firmware: dmi_scan: Pass dmi_entry_point to kexec'ed kernel

Until now kexec'ed kernel has no clue where to look for DMI entry point. Pass it via kernel command line parameter in the same way as it's done for ACPI RSDP. Signed-off-by: Andy Shevchenko --- Documentation/admin-guide/kernel-parameters.txt | 5 + drivers/firmware/dmi_scan.c