Re: [RFC PATCH v9 03/13] mm: Add support for eXclusive Page Frame Ownership (XPFO)
From: Waiman Long <longman@redhat.com>
Date: 2019-05-01 14:49:51
Also in:
linux-arm-kernel, linux-doc, linux-iommu, linux-mm, lkml
Possibly related (same subject, not in this thread)
- 2019-04-22 · Re: [RFC PATCH v9 03/13] mm: Add support for eXclusive Page Frame Ownership (XPFO) · Kees Cook <hidden>
- 2019-04-22 · Re: [RFC PATCH v9 03/13] mm: Add support for eXclusive Page Frame Ownership (XPFO) · Khalid Aziz <hidden>
- 2019-04-18 · Re: [RFC PATCH v9 03/13] mm: Add support for eXclusive Page Frame Ownership (XPFO) · Khalid Aziz <hidden>
- 2019-04-18 · Re: [RFC PATCH v9 03/13] mm: Add support for eXclusive Page Frame Ownership (XPFO) · Thomas Gleixner <hidden>
- 2019-04-18 · Re: [RFC PATCH v9 03/13] mm: Add support for eXclusive Page Frame Ownership (XPFO) · Kees Cook <hidden>
On Wed, Apr 03, 2019 at 11:34:04AM -0600, Khalid Aziz wrote:
quoted hunk ↗ jump to hunk
diff --git a/Documentation/admin-guide/kernel-parameters.txt
b/Documentation/admin-guide/kernel-parameters.txt
quoted hunk ↗ jump to hunk
index 858b6c0b9a15..9b36da94760e 100644--- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt@@ -2997,6 +2997,12 @@nox2apic [X86-64,APIC] Do not enable x2APIC mode. + noxpfo [XPFO] Disable eXclusive Page Frame Ownership (XPFO) + when CONFIG_XPFO is on. Physical pages mapped into + user applications will also be mapped in the + kernel's address space as if CONFIG_XPFO was not + enabled. + cpu0_hotplug [X86] Turn on CPU0 hotplug feature when CONFIG_BO OTPARAM_HOTPLUG_CPU0 is off. Some features depend on CPU0. Known dependencies are:
Given the big performance impact that XPFO can have. It should be off by default when configured. Instead, the xpfo option should be used to enable it. Cheers, Longman