From: boris.ostrovsky@oracle.com
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jason Andryuk <jandryuk@gmail.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] xen: Kconfig: nest Xen guest options
Date: Thu, 15 Oct 2020 09:17:12 -0400 [thread overview]
Message-ID: <b097aec1-e549-a89a-ce43-e9c0a71179f2@oracle.com> (raw)
In-Reply-To: <4e31301b-0e57-ac89-cd71-6ad5e1a66628@citrix.com>
On 10/15/20 9:10 AM, Andrew Cooper wrote:
> On 15/10/2020 13:37, boris.ostrovsky@oracle.com wrote:
>> On 10/14/20 1:53 PM, Jason Andryuk wrote:
>>> +config XEN_512GB
>>> + bool "Limit Xen pv-domain memory to 512GB"
>>> + depends on XEN_PV && X86_64
>> Why is X86_64 needed here?
>> 512G support was implemented using a direct-mapped P2M, and is rather
> beyond the virtual address capabilities of 32bit.
>
Yes, my point was that XEN_PV already depends on X86_64.
-boris
next prev parent reply other threads:[~2020-10-15 13:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 17:53 [PATCH 0/2] Remove Xen PVH dependency on PCI Jason Andryuk
2020-10-14 17:53 ` [PATCH 1/2] xen: Remove Xen PVH/PVHVM " Jason Andryuk
2020-10-15 8:10 ` Jan Beulich
2020-10-15 14:59 ` Jason Andryuk
2020-10-15 15:02 ` Jan Beulich
2020-10-15 15:08 ` Roger Pau Monné
2020-10-14 17:53 ` [PATCH 2/2] xen: Kconfig: nest Xen guest options Jason Andryuk
2020-10-15 9:41 ` Jürgen Groß
2020-10-15 14:52 ` Jason Andryuk
2020-10-15 12:37 ` boris.ostrovsky
2020-10-15 13:10 ` Andrew Cooper
2020-10-15 13:17 ` boris.ostrovsky [this message]
2020-10-15 14:50 ` Jason Andryuk
2020-10-14 18:04 ` [SUSPECTED SPAM][PATCH 0/2] Remove Xen PVH dependency on PCI Andrew Cooper
2020-10-14 19:31 ` Jason Andryuk
2020-12-16 7:01 ` [PATCH " Jürgen Groß
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=b097aec1-e549-a89a-ce43-e9c0a71179f2@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jandryuk@gmail.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
Powered by JetHome