From: Thomas Gleixner <tglx@linutronix.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-mm@kvack.org, mhocko@suse.com, bp@suse.de,
pasha.tatashin@soleen.com, linux-kernel@vger.kernel.org,
dave.hansen@intel.com, torvalds@linux-foundation.org,
hpa@zytor.com, jkosina@suse.cz, ak@linux.intel.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/pti] x86/speculation/l1tf: Drop the swap storage limit restriction when l1tf=off
Date: Tue, 11 Dec 2018 11:47:52 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1812111147300.8611@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20181211090056.GA30493@gmail.com>
On Tue, 11 Dec 2018, Ingo Molnar wrote:
> > off Disables hypervisor mitigations and doesn't emit any
> > warnings.
> > + It also drops the swap size and available RAM limit restrictions
> > + on both hypervisor and bare metal.
> > +
>
> Note tha there's also some whitespace damage here: all other similar
> lines in this RST file start with two tabs, this one starts with 8
> spaces.
Fixed...
next prev parent reply other threads:[~2018-12-11 10:48 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
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 [this message]
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=alpine.DEB.2.21.1812111147300.8611@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=ak@linux.intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=pasha.tatashin@soleen.com \
--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).