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>
Subject: Re: [RFC PATCH 1/8]: PVH: Basic and preparatory changes
Date: Thu, 13 Sep 2012 10:14:39 -0700 [thread overview]
Message-ID: <20120913101439.6bd363a9@mantra.us.oracle.com> (raw)
In-Reply-To: <1347516007.25803.44.camel@dagon.hellion.org.uk>
On Thu, 13 Sep 2012 07:00:07 +0100
Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Wed, 2012-09-12 at 20:32 +0100, Mukesh Rathor wrote:
> > On Wed, 12 Sep 2012 19:26:20 +0100
> > Ian Campbell <Ian.Campbell@citrix.com> wrote:
> >
> > > On Wed, 2012-09-12 at 19:02 +0100, Mukesh Rathor wrote:
> Callback vector is XENFEAT_hvm_callback_vector, I think.
>
> A PV kernel is required to announce the features which it supports via
> the elf notes (defined in xen-head.S).
>
> It would be a bug for the toolstack to enable PVH mode for a kernel
> which did not claim to support the required featureset.
>
> The aim should be that the user should not normally need to specify
> pvh one way or the other, imagine a use case where pygrub is used to
> boot both old and new kernels using it.
>
> The toolstack (or the dom0 builder) can make the determination whether
> to enable this mode itself itself based on the notes (although it is
> always handy to have an override to force things for debug).
Hmmm... So you are suggesting that if hardware and xen supports it, then
PV should just boot in PVH mode and user has no way to override it. I
don't know if that's a good idea in the short term, perhaps in the long
term. Let me discuss with folks here a bit.
thanks,
Mukesh
next prev parent reply other threads:[~2012-09-13 17:14 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
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 [this message]
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=20120913101439.6bd363a9@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Xen-devel@lists.xensource.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).