From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [RFC PATCH 1/8]: PVH: Basic and preparatory changes
Date: Tue, 11 Sep 2012 14:57:51 -0700 [thread overview]
Message-ID: <20120911145751.599b8292@mantra.us.oracle.com> (raw)
In-Reply-To: <1347285352.5305.86.camel@zakaz.uk.xensource.com>
On Mon, 10 Sep 2012 14:55:52 +0100
Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Thu, 2012-08-16 at 01:57 +0100, Mukesh Rathor wrote:
> > diff --git a/include/xen/xen.h b/include/xen/xen.h
> > index a164024..e823639 100644
> > --- a/include/xen/xen.h
> > +++ b/include/xen/xen.h
> > @@ -18,6 +18,10 @@ extern enum xen_domain_type xen_domain_type;
> > xen_domain_type == XEN_PV_DOMAIN)
> > #define xen_hvm_domain() (xen_domain()
> > && \ xen_domain_type == XEN_HVM_DOMAIN)
> > +/* xen_pv_domain check is necessary as start_info ptr is null in
> > HVM. Also,
> > + * note, xen PVH domain shares lot of HVM code */
> > +#define xen_pvh_domain() (xen_pv_domain()
> > && \
> > + (xen_start_info->flags &
> > SIF_IS_PVINHVM))
>
> Can I suggest that for the time being this be gated on a new
> CONFIG_XEN_PVH option (I think it's new, I can't find one right now)
> which "depends EXPERIMENTAL".
>
> We don't want to get into the situation where whatever goes into Linux
> now makes it into a distro (and is enabled) and is subsequently broken
> on top of whatever the final hypervisor side stuff ends up looking
> like. We've done the same for the ARM support for example.
>
> Ian.
Well, I'm pretty much removing all xen_pv_domain() checks and moving to
other checks, like you guys wanted. This code is pretty intermingled and
can't be ifdef'd easily.
Mukesh
next prev parent reply other threads:[~2012-09-11 21:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 0:57 [RFC PATCH 1/8]: PVH: Basic and preparatory changes Mukesh Rathor
2012-08-16 13:59 ` Stefano Stabellini
2012-08-16 18:46 ` Mukesh Rathor
2012-08-17 8:28 ` Ian Campbell
2012-08-17 10:56 ` Stefano Stabellini
2012-08-17 13:48 ` Ian Campbell
2012-08-17 19:17 ` Mukesh Rathor
2012-08-17 10:15 ` Stefano Stabellini
2012-08-17 19:20 ` Mukesh Rathor
2012-08-17 19:36 ` Ian Campbell
2012-08-17 19:36 ` Konrad Rzeszutek Wilk
2012-08-17 22:26 ` Mukesh Rathor
2012-08-18 8:56 ` Ian Campbell
2012-08-20 11:02 ` Stefano Stabellini
2012-08-20 17:50 ` Mukesh Rathor
2012-08-17 8:35 ` Ian Campbell
2012-08-17 19:24 ` Mukesh Rathor
2012-08-17 19:47 ` Ian Campbell
2012-08-17 20:05 ` Konrad Rzeszutek Wilk
2012-08-20 23:42 ` Mukesh Rathor
2012-09-10 13:55 ` Ian Campbell
2012-09-11 21:57 ` Mukesh Rathor [this message]
2012-09-12 8:12 ` Ian Campbell
[not found] ` <20120912110254.10bde333@mantra.us.oracle.com>
[not found] ` <1347474380.25803.21.camel@dagon.hellion.org.uk>
2012-09-12 19:32 ` Mukesh Rathor
2012-09-13 6:00 ` Ian Campbell
2012-09-13 17:14 ` Mukesh Rathor
2012-09-13 17:36 ` Pasi Kärkkäinen
2012-09-13 18:08 ` Ian Campbell
2012-09-13 20:45 ` Konrad Rzeszutek Wilk
2012-09-13 21:09 ` Ian Campbell
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=20120911145751.599b8292@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
/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).