From: Michal Hocko <mhocko@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jiri Kosina <jikos@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Andi Kleen <ak@linux.intel.com>, Borislav Petkov <bp@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] l1tf: drop the swap storage limit restriction when l1tf=off
Date: Mon, 10 Dec 2018 21:03:20 +0100 [thread overview]
Message-ID: <20181210200320.GX1286@dhcp22.suse.cz> (raw)
In-Reply-To: <nycvar.YFH.7.76.1812092145510.17216@cbobk.fhfr.pm>
On Sun 09-12-18 21:46:57, Jiri Kosina wrote:
> On Mon, 19 Nov 2018, Michal Hocko wrote:
>
> > > > > > + 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@suse.cz>
> > > >
> > > > Thanks!
> > >
> > > Yes, I think that makes it absolutely clear. Thanks,
> >
> > OK. Here is the incremental diff on top of the patch. I will fold and
> > repost later this week. I assume people are still catching up after LPC
> > and I do not want to spam them even more.
>
> Is this queued anywhere in the meantime please?
Not yet. Thanks for the reminder. It completely fall of my radar.
Thomas, do you want me to resubmit or there are some other changes you
would like to see?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-12-10 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 18:49 [PATCH] l1tf: drop the swap storage limit restriction when l1tf=off Michal Hocko
2018-11-13 19:20 ` Pavel Tatashin
2018-11-13 19:56 ` Jiri Kosina
2018-11-14 7:32 ` Michal Hocko
2018-11-19 13:36 ` Jiri Kosina
2018-11-19 13:51 ` Michal Hocko
2018-12-09 20:46 ` Jiri Kosina
2018-12-10 20:03 ` Michal Hocko [this message]
2018-11-15 0:27 ` Andi Kleen
2018-12-10 21:09 ` [tip:x86/pti] x86/speculation/l1tf: Drop " tip-bot for Michal Hocko
2018-12-11 9:00 ` Ingo Molnar
2018-12-11 10:47 ` Thomas Gleixner
2018-12-11 11:13 ` Michal Hocko
2018-12-11 10:36 ` tip-bot for Michal Hocko
2018-12-11 10:51 ` tip-bot for Michal Hocko
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=20181210200320.GX1286@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=ak@linux.intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).