From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: RFC: xen config changes v4
Date: Fri, 27 Feb 2015 12:48:56 +0000 [thread overview]
Message-ID: <1425041336.14641.178.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1502271215060.23507@kaball.uk.xensource.com>
On Fri, 2015-02-27 at 12:24 +0000, Stefano Stabellini wrote:
> > Using PV frontends is completely orthogonal to other PV enhancements
> > like PARAVIRT_CLOCK, HVMOP_pagetable_dying or PV IPIs. So why do you
> > object enabling the PV frontends for those kernels?
>
> I am for it. I would like to avoid two user visible XEN enablement
> options (XEN_FRONTEND vs. XEN_PVHVM) for x86_64 and PAE HVM guests to
> avoid configurations with just XEN_FRONTEND, that can be considered a
> performance regression compared to what we have now (on x86_64 and PAE).
Probably some suitable select/depends could be used to allow this
configuration only for non-PAE/x86_32 and x86_64 configurations?
Ian.
next prev parent reply other threads:[~2015-02-27 12:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 1:53 RFC: xen config changes v4 Luis R. Rodriguez
2015-02-26 4:59 ` Juergen Gross
2015-02-26 10:08 ` David Vrabel
2015-02-26 11:08 ` Stefano Stabellini
2015-02-26 17:29 ` Luis R. Rodriguez
2015-02-26 17:42 ` Stefano Stabellini
2015-02-26 18:48 ` Luis R. Rodriguez
2015-02-27 6:14 ` Juergen Gross
2015-02-27 21:33 ` Luis R. Rodriguez
2015-02-27 10:04 ` Ian Campbell
2015-02-27 6:09 ` Juergen Gross
2015-02-27 9:41 ` Stefano Stabellini
2015-02-27 9:55 ` Juergen Gross
2015-02-27 10:11 ` Stefano Stabellini
2015-02-27 10:30 ` Ian Campbell
2015-02-27 11:27 ` Stefano Stabellini
2015-02-27 11:30 ` Juergen Gross
2015-02-27 12:24 ` Stefano Stabellini
2015-02-27 12:36 ` Juergen Gross
2015-02-27 13:38 ` Stefano Stabellini
2015-02-27 14:30 ` Juergen Gross
2015-02-27 17:53 ` Luis R. Rodriguez
2015-02-27 18:27 ` Konrad Rzeszutek Wilk
2015-03-02 9:55 ` Stefano Stabellini
2015-03-02 16:07 ` Konrad Rzeszutek Wilk
2015-03-02 17:07 ` Stefano Stabellini
2015-03-02 17:30 ` Konrad Rzeszutek Wilk
2015-03-02 21:15 ` Luis R. Rodriguez
2015-03-03 6:59 ` Juergen Gross
2015-03-02 21:08 ` Luis R. Rodriguez
2015-03-02 20:39 ` Luis R. Rodriguez
2015-03-06 17:17 ` Luis R. Rodriguez
2015-03-06 18:02 ` Konrad Rzeszutek Wilk
2015-03-06 18:08 ` Luis R. Rodriguez
2015-03-06 18:24 ` Roger Pau Monné
2015-02-27 12:48 ` Ian Campbell [this message]
2015-02-27 18:18 ` Konrad Rzeszutek Wilk
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=1425041336.14641.178.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=mcgrof@suse.com \
--cc=stefano.stabellini@eu.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 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.