From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Li Zhijian <zhijianx.li@intel.com>,
Juergen Gross <jgross@suse.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
Peter Maydell <peter.maydell@linaro.org>,
x86@kernel.org, bp@alien8.de, mingo@redhat.com,
tglx@linutronix.de, QEMU Developers <qemu-devel@nongnu.org>,
Philip Li <philip.li@intel.com>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Kees Cook <keescook@chromium.org>
Subject: Re: [Qemu-devel] [RFC/PoC PATCH 1/3] i386: set initrd_max to 4G - 1 to allow up to 4G initrd
Date: Sun, 11 Nov 2018 22:36:27 -0800 [thread overview]
Message-ID: <766e1f84-b8c0-db95-45d3-e624c8d61519@zytor.com> (raw)
In-Reply-To: <20181112061940.GA61749@gmail.com>
On 11/11/18 10:19 PM, Ingo Molnar wrote:
>
> I might be a bit dense early in the morning, but could you elaborate?
> What do you mean by mapping all data areas?
>
Heh. I need to pack for LPC and get some sleep before my flight lest I'll be
denser than depleted uranium; I'll write an explanation tomorrow.
-hpa
next prev parent reply other threads:[~2018-11-12 6:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1541674784-25936-1-git-send-email-lizhijian@cn.fujitsu.com>
[not found] ` <1541674784-25936-2-git-send-email-lizhijian@cn.fujitsu.com>
[not found] ` <CAFEAcA_47wyar3WNhuBmNPdr02RHx-wn_TeyFaajpjzvzG8j5Q@mail.gmail.com>
2018-11-09 1:47 ` Li Zhijian
2018-11-09 7:20 ` Ingo Molnar
2018-11-09 9:57 ` Li Zhijian
2018-11-09 10:04 ` Juergen Gross
2018-11-09 13:11 ` Li Zhijian
2018-11-09 13:40 ` Li Zhijian
2018-11-09 21:10 ` H. Peter Anvin
2018-11-12 4:56 ` Ingo Molnar
2018-11-12 6:00 ` H. Peter Anvin
2018-11-12 6:19 ` Ingo Molnar
2018-11-12 6:36 ` H. Peter Anvin [this message]
2018-11-12 16:47 ` H. Peter Anvin
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=766e1f84-b8c0-db95-45d3-e624c8d61519@zytor.com \
--to=hpa@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bp@alien8.de \
--cc=jgross@suse.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhijian@cn.fujitsu.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philip.li@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=zhijianx.li@intel.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
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
all inboxes | Powered by JetHome®