From: "Jürgen Groß" <jgross@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>, linux-kernel@vger.kernel.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/2] Revert "xen: fix p2m size in dom0 for disabled memory hotplug case"
Date: Tue, 23 Mar 2021 07:43:26 +0100 [thread overview]
Message-ID: <be20366d-8640-a309-259b-6a0e94661cf4@suse.com> (raw)
In-Reply-To: <20210317110401.46322-3-roger.pau@citrix.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 522 bytes --]
On 17.03.21 12:04, Roger Pau Monne wrote:
> This partially reverts commit 882213990d32fd224340a4533f6318dd152be4b2.
>
> There's no need to special case XEN_UNPOPULATED_ALLOC anymore in order
> to correctly size the p2m. The generic memory hotplug option has
> already been tied together with the Xen hotplug limit, so enabling
> memory hotplug should already trigger a properly sized p2m on Xen PV.
Can you add some words here that XEN_UNPOPULATED_ALLOC depends on
MEMORY_HOTPLUG via ZONE_DEVICE?
Juergen
[-- Attachment #1.1.2: OpenPGP_0xB0DE9DD628BF132F.asc --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2021-03-23 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 11:03 [PATCH 0/2] xen/x86: alternative fix for XSA-369 Roger Pau Monne
2021-03-17 11:04 ` [PATCH 1/2] xen/x86: make XEN_BALLOON_MEMORY_HOTPLUG_LIMIT depend on MEMORY_HOTPLUG Roger Pau Monne
2021-03-17 11:04 ` [PATCH 2/2] Revert "xen: fix p2m size in dom0 for disabled memory hotplug case" Roger Pau Monne
2021-03-22 19:09 ` Boris Ostrovsky
2021-03-23 6:43 ` Jürgen Groß [this message]
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=be20366d-8640-a309-259b-6a0e94661cf4@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@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;
as well as URLs for NNTP newsgroup(s).