[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXOLYL8D=-iBzg+SKnAwefP_uTHNh31UCHTSQg24VCQig@mail.gmail.com>
Date: Wed, 5 Dec 2012 16:22:00 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org, linux-efi@...r.kernel.org,
mfleming@...el.com, dwmw2@...radead.org,
"H. Peter Anvin" <hpa@...or.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: Use PCI ROMs from EFI boot services
On Wed, Dec 5, 2012 at 4:18 PM, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> On Wed, Dec 05, 2012 at 04:15:56PM -0800, Yinghai Lu wrote:
>
>> at the same time we should export setup_data into /sys, so kexec could
>> append this pointer to command of
>> second kernel, just like kexec append acpi_rsdp.
>> That should address DavidW's concern.
>
> Why should the kernel export data to userspace just so that that data
> can be passed back into the kernel?
then how the kexeced get those info?
first kernel already reserved those info as E820_RESERVED_KERN.
and those info are for bootloader's of first kernel.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists