From: "Jürgen Groß" <jgross@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Ian Jackson <ian.jackson@citrix.com>
Subject: Re: [Xen-devel] [PATCH OSSTEST] kernel-build: enable XEN_BALLOON_MEMORY_HOTPLUG
Date: Tue, 24 Mar 2020 14:08:23 +0100 [thread overview]
Message-ID: <40b9a119-a787-2e4b-8383-87510a9cccb9@suse.com> (raw)
In-Reply-To: <20200324120050.GK24458@Air-de-Roger.citrite.net>
On 24.03.20 13:00, Roger Pau Monné wrote:
> Adding Juergen and Boris for feedback.
>
> On Tue, Mar 24, 2020 at 11:57:48AM +0000, Ian Jackson wrote:
>> Ian Jackson writes ("Re: [PATCH OSSTEST] kernel-build: enable XEN_BALLOON_MEMORY_HOTPLUG"):
>>> Roger Pau Monne writes ("[PATCH OSSTEST] kernel-build: enable XEN_BALLOON_MEMORY_HOTPLUG"):
>>>> This allows a PVH/HVM domain to use unpopulated memory ranges to map
>>>> foreign memory or grants, and is required for a PVH dom0 to function
>>>> properly.
>>>>
>>>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>>>
>>> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>>>
>>> I will push this to pretest immediately.
>>
>> Now done. Would you consider whether the default should be changed
>> in Linux and prepare a patch to do so if appropriate ?
>
> DYK if there's any reason why this is not on by default?
AFAIK the default has been off since introduction in 2011.
I don't know the reason for that.
Juergen
prev parent reply other threads:[~2020-03-24 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 14:38 [Xen-devel] [PATCH OSSTEST] kernel-build: enable XEN_BALLOON_MEMORY_HOTPLUG Roger Pau Monne
2020-03-24 11:55 ` Ian Jackson
[not found] ` <24185.62908.869446.447190@mariner.uk.xensource.com>
2020-03-24 12:00 ` Roger Pau Monné
2020-03-24 13:08 ` 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=40b9a119-a787-2e4b-8383-87510a9cccb9@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@citrix.com \
--cc=roger.pau@citrix.com \
--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).