From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 17/18 V2]: PVH xen: PVH dom0 creation...
Date: Tue, 19 Mar 2013 09:32:19 -0400 [thread overview]
Message-ID: <20130319133219.GE2706@phenom.dumpdata.com> (raw)
In-Reply-To: <51483D9602000078000C6A56@nat28.tlf.novell.com>
On Tue, Mar 19, 2013 at 09:27:34AM +0000, Jan Beulich wrote:
> >>> On 16.03.13 at 02:06, Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
> > Finally, the hardest. Mostly modify construct_dom0() to boot PV dom0 in
> > PVH mode. Introduce, opt_dom0pvh, which when specified in the command
> > line, causes dom0 to boot in PVH mode.
>
> Now that Konrad mentioned that PVH is intended for 64-bit guests
> only, I fail to see where this restriction is being enforced in this
> patch. And it would certainly have been worthwhile to state that
> more prominently, even more so since Konrad keeps telling people
> that this patch set is expected to initiate a deprecation phase for
> the PV MMU interfaces in Linux (which then would mean no 32-bit
> PV guest support at all anymore).
It was not in my mind for the first stage of this work, thought I
have to admit that the 32-bit part completly vanished in my mind.
You are right - we need then 32-bit support otherwise we are screwed in
the X years we initiate the deprecation phase in the upstream
PV MMU interface.
I was not expecting that this set of patches would be the 'ok, the
timer for deprecation is ticking once the patch goes in Xen' - rather
when folks agree that it is the right time.
next prev parent reply other threads:[~2013-03-19 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 1:06 [PATCH 17/18 V2]: PVH xen: PVH dom0 creation Mukesh Rathor
2013-03-18 13:01 ` Jan Beulich
2013-03-27 0:34 ` Mukesh Rathor
2013-03-29 0:32 ` Mukesh Rathor
2013-04-02 7:03 ` Jan Beulich
2013-03-18 20:06 ` Konrad Rzeszutek Wilk
2013-03-26 23:25 ` Mukesh Rathor
2013-03-19 9:27 ` Jan Beulich
2013-03-19 13:32 ` Konrad Rzeszutek Wilk [this message]
2013-03-26 23:42 ` Mukesh Rathor
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=20130319133219.GE2706@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.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.