From: George Dunlap <george.dunlap@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 4/4] x86/PoD: Command line option to prohibit any PoD operations
Date: Mon, 2 Nov 2015 15:19:49 +0000 [thread overview]
Message-ID: <56377F15.5070804@citrix.com> (raw)
In-Reply-To: <1446230022-8349-5-git-send-email-andrew.cooper3@citrix.com>
On 30/10/15 18:33, Andrew Cooper wrote:
> PoD is only needed to cover a corner case with memory overcommit
> (rebooting a ballooned down VM with insufficient host RAM available).
>
> Its use comes with a performance hit, and inoperability with other
> technologies such as PCI Passthrough.
>
> Offer a command line option for administrators who want to be certain
> that PoD is not in use for their VMs.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
With the arm build addressed:
Acked-by: George Dunlap <george.dunlap@citrix.com>
prev parent reply other threads:[~2015-11-02 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 18:33 [PATCH 0/4] Futher work after XSA-150 Andrew Cooper
2015-10-30 18:33 ` [PATCH 1/4] x86/PoD: Make p2m_pod_empty_cache() restartable Andrew Cooper
2015-11-02 12:17 ` George Dunlap
2015-10-30 18:33 ` [PATCH 2/4] x86/PoD: Identify when a domain has already been killed from PoD exhaustion Andrew Cooper
2015-11-02 14:07 ` George Dunlap
2015-11-02 14:32 ` Andrew Cooper
2015-11-23 14:50 ` Jan Beulich
2015-11-24 16:51 ` George Dunlap
2015-10-30 18:33 ` [PATCH 3/4] x86/mm: Return -ESRCH for an invalid foreign domid Andrew Cooper
2015-11-02 14:10 ` George Dunlap
2015-10-30 18:33 ` [PATCH 4/4] x86/PoD: Command line option to prohibit any PoD operations Andrew Cooper
2015-11-02 13:53 ` Jan Beulich
2015-11-02 14:32 ` Ian Campbell
2015-11-02 14:37 ` Andrew Cooper
2015-11-02 14:38 ` Jan Beulich
2015-11-02 15:19 ` George Dunlap [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=56377F15.5070804@citrix.com \
--to=george.dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.