From: Ian Campbell <Ian.Campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH V3 1/6]: PVH: basic and header changes, elfnote changes, ...
Date: Tue, 23 Oct 2012 09:51:41 +0100 [thread overview]
Message-ID: <1350982301.2237.6.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20121019131707.GG26830@phenom.dumpdata.com>
On Fri, 2012-10-19 at 14:17 +0100, Konrad Rzeszutek Wilk wrote:
> > > +config XEN_X86_PVH
> > > + bool "Support for running as a PVH guest (EXPERIMENTAL)"
> > > + depends on X86_64 && XEN && EXPERIMENTAL
> > > + default n
> > > + help
> > > + This option enables support for running as a PVH guest (PV guest
> > > + using hardware extensions) under a suitably capable hypervisor.
> > > + This option is EXPERIMENTAL because the hypervisor interfaces
> > > + which it uses are not yet considered stable therefore backwards and
> > > + forwards compatibility is not yet guaranteed. If unsure, say N.
> >
> > Do we really need the kconfig symbol? Why can't we have it always
>
> Yes for right now. That is to make sure that we can test for regressions
> PV guests on a hypervisor without PVH extensions - or vice-versa:
> PVH hypervisors with an normal PV guest.
Also the "depends on X86_64" bit is currently quite important...
Ian.
next prev parent reply other threads:[~2012-10-23 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 0:26 Mukesh Rathor
2012-10-18 10:57 ` Stefano Stabellini
2012-10-19 13:17 ` Konrad Rzeszutek Wilk
2012-10-19 15:53 ` Stefano Stabellini
2012-10-23 8:51 ` Ian Campbell [this message]
2012-10-19 13:07 ` 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=1350982301.2237.6.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®