From: Ard Biesheuvel <email@example.com> To: Dan Williams <firstname.lastname@example.org> Cc: linux-nvdimm <email@example.com>, "the arch/x86 maintainers" <firstname.lastname@example.org>, Linux Kernel Mailing List <email@example.com>, Linux-MM <firstname.lastname@example.org>, Ingo Molnar <email@example.com>, Borislav Petkov <firstname.lastname@example.org>, "H. Peter Anvin" <email@example.com>, Darren Hart <firstname.lastname@example.org>, Thomas Gleixner <email@example.com>, Andy Shevchenko <firstname.lastname@example.org> Subject: Re: [RFC PATCH 1/5] efi: Detect UEFI 2.8 Special Purpose Memory Date: Fri, 12 Apr 2019 13:43:42 -0700 Message-ID: <CAKv+Gu_gzHH7onY4WUWV8SAYeVXfMK-W3CaxYZ706sPo6ATZpA@mail.gmail.com> (raw) In-Reply-To: <CAA9_cmeRqr=b-hmaxA0aLZE98YGS9hF8h8JGGp9K6c_qhLK3AQ@mail.gmail.com> On Tue, 9 Apr 2019 at 19:11, Dan Williams <email@example.com> wrote: > > On Tue, Apr 9, 2019 at 10:21 AM Ard Biesheuvel > <firstname.lastname@example.org> wrote: > > > > On Tue, 9 Apr 2019 at 09:44, Dan Williams <email@example.com> wrote: > > > > > > On Fri, Apr 5, 2019 at 9:21 PM Ard Biesheuvel <firstname.lastname@example.org> wrote: > > > > > > > > Hi Dan, > > > > > > > > On Thu, 4 Apr 2019 at 21:21, Dan Williams <email@example.com> wrote: > > > > > > > > > > UEFI 2.8 defines an EFI_MEMORY_SP attribute bit to augment the > > > > > interpretation of the EFI Memory Types as "reserved for a special > > > > > purpose". > > > > > > > > > > The proposed Linux behavior for special purpose memory is that it is > > > > > reserved for direct-access (device-dax) by default and not available for > > > > > any kernel usage, not even as an OOM fallback. Later, through udev > > > > > scripts or another init mechanism, these device-dax claimed ranges can > > > > > be reconfigured and hot-added to the available System-RAM with a unique > > > > > node identifier. > > > > > > > > > > A follow-on patch integrates parsing of the ACPI HMAT to identify the > > > > > node and sub-range boundaries of EFI_MEMORY_SP designated memory. For > > > > > now, arrange for EFI_MEMORY_SP memory to be reserved. > > > > > > > > > > Cc: Thomas Gleixner <firstname.lastname@example.org> > > > > > Cc: Ingo Molnar <email@example.com> > > > > > Cc: Borislav Petkov <firstname.lastname@example.org> > > > > > Cc: "H. Peter Anvin" <email@example.com> > > > > > Cc: Ard Biesheuvel <firstname.lastname@example.org> > > > > > Cc: Darren Hart <email@example.com> > > > > > Cc: Andy Shevchenko <firstname.lastname@example.org> > > > > > Signed-off-by: Dan Williams <email@example.com> > > > > > --- > > > > > arch/x86/Kconfig | 18 ++++++++++++++++++ > > > > > arch/x86/boot/compressed/eboot.c | 5 ++++- > > > > > arch/x86/boot/compressed/kaslr.c | 2 +- > > > > > arch/x86/include/asm/e820/types.h | 9 +++++++++ > > > > > arch/x86/kernel/e820.c | 9 +++++++-- > > > > > arch/x86/platform/efi/efi.c | 10 +++++++++- > > > > > include/linux/efi.h | 14 ++++++++++++++ > > > > > include/linux/ioport.h | 1 + > > > > > 8 files changed, 63 insertions(+), 5 deletions(-) > > > > > > > > > > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig > > > > > index c1f9b3cf437c..cb9ca27de7a5 100644 > > > > > --- a/arch/x86/Kconfig > > > > > +++ b/arch/x86/Kconfig > > > > > @@ -1961,6 +1961,24 @@ config EFI_MIXED > > > > > > > > > > If unsure, say N. > > > > > > > > > > +config EFI_SPECIAL_MEMORY > > > > > + bool "EFI Special Purpose Memory Support" > > > > > + depends on EFI > > > > > + ---help--- > > > > > + On systems that have mixed performance classes of memory EFI > > > > > + may indicate special purpose memory with an attribute (See > > > > > + EFI_MEMORY_SP in UEFI 2.8). A memory range tagged with this > > > > > + attribute may have unique performance characteristics compared > > > > > + to the system's general purpose "System RAM" pool. On the > > > > > + expectation that such memory has application specific usage > > > > > + answer Y to arrange for the kernel to reserve it for > > > > > + direct-access (device-dax) by default. The memory range can > > > > > + later be optionally assigned to the page allocator by system > > > > > + administrator policy. Say N to have the kernel treat this > > > > > + memory as general purpose by default. > > > > > + > > > > > + If unsure, say Y. > > > > > + > > > > > > > > EFI_MEMORY_SP is now part of the UEFI spec proper, so it does not make > > > > sense to make any understanding of it Kconfigurable. > > > > > > No, I think you're misunderstanding what this Kconfig option is trying > > > to achieve. > > > > > > The configuration capability is solely for the default kernel policy. > > > As can already be seen by Christoph's response  the thought that > > > the firmware gets more leeway to dictate to Linux memory policy may be > > > objectionable. > > > > > > : https://lore.kernel.org/lkml/20190409121318.GA16955@infradead.org/ > > > > > > So the Kconfig option is gating whether the kernel simply ignores the > > > attribute and gives it to the page allocator by default. Anything > > > fancier, like sub-dividing how much is OS managed vs device-dax > > > accessed requires the OS to reserve it all from the page-allocator by > > > default until userspace policy can be applied. > > > > > > > I don't think this policy should dictate whether we pretend that the > > attribute doesn't exist in the first place. We should just wire up the > > bit fully, and only apply this policy at the very end. > > The bit is just a policy hint, if the kernel is not implementing any > of the policy why even check for the bit? > Because I would like things like the EFI memory map dumping code etc to report the bit regardless of whether we are honoring it or not. > > > > > > Instead, what I would prefer is to implement support for EFI_MEMORY_SP > > > > unconditionally (including the ability to identify it in the debug > > > > dump of the memory map etc), in a way that all architectures can use > > > > it. Then, I think we should never treat it as ordinary memory and make > > > > it the firmware's problem not to use the EFI_MEMORY_SP attribute in > > > > cases where it results in undesired behavior in the OS. > > > > > > No, a policy of "never treat it as ordinary memory" confuses the base > > > intent of the attribute which is an optional hint to get the OS to not > > > put immovable / non-critical allocations in what could be a precious > > > resource. > > > > > > > The base intent is to prevent the OS from using memory that is > > co-located with an accelerator for any purpose other than what the > > accelerator needs it for. Having a Kconfigurable policy that may be > > disabled kind of misses the point IMO. I think 'optional hint' doesn't > > quite capture the intent. > > That's not my understanding, and an EFI attribute is the wrong > mechanism to meet such a requirement. If this memory is specifically > meant for use with a given accelerator then it had better be marked > reserved and the accelerator driver is then responsible for publishing > the resource to the OS if at all. > > You did prompt me to go back and re-read the wording in the spec. It > still seems clear to me that the attribute is an optional hint not a > hard requirement. Whether the OS honors an optional hint is an OS > policy and I fail to see why the OS should bother to detect the bit > without implementing any associated policy. > Because not taking a hint is not the same thing as pretending it isn't there to begin with. > > > Moreover, the interface for platform firmware to indicate that a > > > memory range should never be treated as ordinary memory is simply the > > > existing "reserved" memory type, not this attribute. That's the > > > mechanism to use when platform firmware knows that a driver is needed > > > for a given mmio resource. > > > > > > > Reserved memory is memory that simply should never touched at all by > > the OS, and on ARM, we take care never to map it anywhere. > > That's not a guarantee, at least on x86. Some shipping persistent > memory platforms describe it as reserved and then the ACPI NFIT > further describes what that reserved memory contains and how the OS > can use it. See commit af1996ef59db "ACPI: Change NFIT driver to > insert new resource". The UEFI spec is pretty clear about the fact that reserved memory shouldn't ever be touched by the OS. The fact that x86 platforms exist that violate this doesn't mean we should abuse it in other ways as well.
next prev parent reply index Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-04 19:08 [RFC PATCH 0/5] EFI Special Purpose Memory Support Dan Williams 2019-04-04 19:08 ` [RFC PATCH 1/5] efi: Detect UEFI 2.8 Special Purpose Memory Dan Williams 2019-04-06 4:21 ` Ard Biesheuvel 2019-04-09 16:43 ` Dan Williams 2019-04-09 17:21 ` Ard Biesheuvel 2019-04-10 2:10 ` Dan Williams 2019-04-12 20:43 ` Ard Biesheuvel [this message] 2019-04-12 21:18 ` Dan Williams 2019-04-15 11:43 ` Enrico Weigelt, metux IT consult 2019-04-04 19:08 ` [RFC PATCH 2/5] lib/memregion: Uplevel the pmem "region" ida to a global allocator Dan Williams 2019-04-04 19:32 ` Matthew Wilcox 2019-04-04 21:02 ` Dan Williams 2019-04-04 19:08 ` [RFC PATCH 3/5] acpi/hmat: Track target address ranges Dan Williams 2019-04-04 20:58 ` Keith Busch 2019-04-04 20:58 ` Dan Williams 2019-04-04 19:08 ` [RFC PATCH 4/5] acpi/hmat: Register special purpose memory as a device Dan Williams 2019-04-05 11:18 ` Jonathan Cameron 2019-04-05 15:43 ` Dan Williams 2019-04-05 16:23 ` Jonathan Cameron 2019-04-05 16:56 ` Dan Williams 2019-04-05 17:39 ` Jonathan Cameron 2019-04-09 12:13 ` Christoph Hellwig 2019-04-09 14:49 ` Dan Williams 2019-04-04 19:08 ` [RFC PATCH 5/5] device-dax: Add a driver for "hmem" devices Dan Williams
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=CAKv+Gu_gzHH7onY4WUWV8SAYeVXfMK-W3CaxYZ706sPo6ATZpA@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
LKML Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \ firstname.lastname@example.org public-inbox-index lkml Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git