From: Toshi Kani <toshi.kani@hpe.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Elliott, Robert (Persistent Memory)" <elliott@hpe.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] ACPI/Kconfig: Make ACPI_NFIT depend on EFI_STUB on X86
Date: Tue, 15 Dec 2015 10:49:39 -0700 [thread overview]
Message-ID: <1450201779.29051.28.camel@hpe.com> (raw)
In-Reply-To: <CAPcyv4i_uRBsceQ1bqd02orKwZ47qB_ggwRQFL0HQ0x=w1DPfQ@mail.gmail.com>
On Tue, 2015-12-15 at 09:21 -0800, Dan Williams wrote:
> On Tue, Dec 15, 2015 at 8:59 AM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > ACPI 6.0 defines NFIT table and new persistent memory types for
> > EFI memory table (EFI_PERSISTENT_MEMORY) and e820 table (E820_PMEM).
> >
> > setup_e820() enabled by EFI_STUB converts EFI_PERSISTENT_MEMORY to
> > E820_PMEM for the e820_map table on x86 EFI platforms. When EFI_STUB
> > is disabled, x86 kernels rely on the bootloader to perform this
> > conversion.
> >
> > It was found that the upstream grub bootloader since 2012 has a bug
> > that converts EFI_PERSISTENT_MEMORY (or any new type) to E820_RAM,
> > which causes the kernel to use persistent memory ranges as regular
> > memory and corrupts the data in NVDIMM.
> >
> > Therefore, this patch sets ACPI_NFIT to depend on EFI_STUB on x86.
> > This assures that ACPI_NFIT kernels are self-contained and are
> > protected from the upstream grub bug on x86.
> >
> > Note, X86_PMEM_LEGACY allows the kernel to use the pmem driver on
> > pre-ACPI 6.0 platforms, and does not require ACPI_NFIT enabled.
> >
> > References:
> > http://www.mail-archive.com/grub-devel@gnu.org/msg23961.html
> > Reported-by: Robert Elliott <elliott@hpe.com>
> > Signed-off-by: Toshi Kani <toshi.kani@hpe.com>
> > Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > ---
> > drivers/acpi/Kconfig | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
> > index 5eef4cb..5368baa 100644
> > --- a/drivers/acpi/Kconfig
> > +++ b/drivers/acpi/Kconfig
> > @@ -441,6 +441,7 @@ config ACPI_NFIT
> > depends on PHYS_ADDR_T_64BIT
> > depends on BLK_DEV
> > depends on ARCH_HAS_MMIO_FLUSH
> > + depends on !X86 || (X86 && EFI_STUB)
> > select LIBNVDIMM
> > help
> > Infrastructure to probe ACPI 6 compliant platforms for
>
> This seems wrong to me.
>
> In general Kconfig "depends on" are only about compile-time code
> dependency, not about working around random bugs in external projects.
I agree that they do not have a compile dependency, and it looks rather
odd. On the other hand, proper support of the ACPI NFIT extensions has a
functional dependency to setup_e820() as this is the only code that can
handle the EFI_PERSISTENT_MEMORY type today.
Thanks,
-Toshi
next prev parent reply other threads:[~2015-12-15 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 16:59 [PATCH RESEND] ACPI/Kconfig: Make ACPI_NFIT depend on EFI_STUB on X86 Toshi Kani
2015-12-15 17:21 ` Dan Williams
2015-12-15 17:49 ` Toshi Kani [this message]
2015-12-15 17:53 ` Dan Williams
2015-12-15 17:56 ` Toshi Kani
2015-12-15 18:05 ` Dan Williams
2015-12-15 20:04 ` Toshi Kani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1450201779.29051.28.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=elliott@hpe.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox