On Tue 13-11-18 20:56:54, Jiri Kosina wrote: > On Tue, 13 Nov 2018, Michal Hocko wrote: > > > From: Michal Hocko <mhocko@xxxxxxxx> > > > > Swap storage is restricted to max_swapfile_size (~16TB on x86_64) > > whenever the system is deemed affected by L1TF vulnerability. Even > > though the limit is quite high for most deployments it seems to be > > too restrictive for deployments which are willing to live with the > > mitigation disabled. > > > > We have a customer to deploy 8x 6,4TB PCIe/NVMe SSD swap devices > > which is clearly out of the limit. > > > > Drop the swap restriction when l1tf=off is specified. It also doesn't > > make much sense to warn about too much memory for the l1tf mitigation > > when it is forcefully disabled by the administrator. > > > > Signed-off-by: Michal Hocko <mhocko@xxxxxxxx> > > --- > > Documentation/admin-guide/kernel-parameters.txt | 2 ++ > > Documentation/admin-guide/l1tf.rst | 5 ++++- > > arch/x86/kernel/cpu/bugs.c | 3 ++- > > arch/x86/mm/init.c | 2 +- > > 4 files changed, 9 insertions(+), 3 deletions(-) > > > > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt > > index 81d1d5a74728..a54f2bd39e77 100644 > > --- a/Documentation/admin-guide/kernel-parameters.txt > > +++ b/Documentation/admin-guide/kernel-parameters.txt > > @@ -2095,6 +2095,8 @@ > > off > > Disables hypervisor mitigations and doesn't > > emit any warnings. > > + It also drops the swap size and available > > + RAM limit restriction. > > Minor nit: I think this should explicitly mention that those two things > are related to bare metal mitigation, to avoid any confusion (as otherwise > the l1tf cmdline parameter is purely about hypervisor mitigations). Do you have any specific wording in mind? It also drops the swap size and available RAM limit restrictions on both hypervisor and bare metal. Sounds better? > With that > > Acked-by: Jiri Kosina <jkosina@xxxxxxx> Thanks! -- Michal Hocko SUSE Labs
