From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"mukesh.rathor@oracle.com" <mukesh.rathor@oracle.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH V5] PVH patches for v3.8.
Date: Wed, 24 Oct 2012 10:34:39 +0100 [thread overview]
Message-ID: <1351071279.2237.126.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <5087B13402000078000A3CBB@nat28.tlf.novell.com>
On Wed, 2012-10-24 at 08:13 +0100, Jan Beulich wrote:
> > include/xen/interface/memory.h | 29 ++++++-
> > include/xen/interface/physdev.h | 10 ++
>
> ... any changes to the hypervisor interface (didn't look in detail
> what is being changed in these two headers) should first be in
> at least -unstable before being consumed in any official release
> imo.
I'd also like to see at least the interface definitions in the h/v tree
if not the implementation right away.
The flip side is that we have agreed that the interfaces are not
considered set in stone / stable until we've had a chance to review the
implementation, so perhaps it is better not to commit them to
xen-unstable.hg right away.
I don't know what the right answer is. Perhaps we should at a minimum
reserve the subop numbers even if we don't yet define what they mean in
the Xen tree.
Ian.
next prev parent reply other threads:[~2012-10-24 9:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 18:12 Konrad Rzeszutek Wilk
2012-10-23 18:12 ` [PATCH 01/10] xen/pvh: Support ParaVirtualized Hardware extensions Konrad Rzeszutek Wilk
2012-10-24 9:37 ` Ian Campbell
2012-10-29 13:46 ` Konrad Rzeszutek Wilk
2012-10-23 18:12 ` [PATCH 02/10] xen/pvh: Fix PVHVM 32-bit bootup problems Konrad Rzeszutek Wilk
2012-10-24 11:01 ` Stefano Stabellini
2012-10-23 18:12 ` [PATCH 03/10] xen/hypercall: Make xen_remove_from_physmap the same on 64/32 builds Konrad Rzeszutek Wilk
2012-10-24 9:40 ` Ian Campbell
2012-10-24 11:02 ` Stefano Stabellini
2012-10-29 13:50 ` Konrad Rzeszutek Wilk
2012-10-23 18:12 ` [PATCH 04/10] xen/smp: Move the common CPU init code a bit to prep for PVH patch Konrad Rzeszutek Wilk
2012-10-23 18:12 ` [PATCH 05/10] xen/pvh: Extend vcpu_guest_context, p2m, event, and XenBus Konrad Rzeszutek Wilk
2012-10-24 9:49 ` Ian Campbell
2012-10-23 18:12 ` [PATCH 06/10] xen/pvh: Implement MMU changes for PVH Konrad Rzeszutek Wilk
2012-10-23 18:12 ` [PATCH 07/10] xen/pvh: bootup and setup (E820) related changes Konrad Rzeszutek Wilk
2012-10-23 18:12 ` [PATCH 08/10] xen/e820: Coalesce the PVH release/populate logic in the generic case Konrad Rzeszutek Wilk
2012-10-23 18:12 ` [PATCH 09/10] xen/pvh: balloon and grant changes Konrad Rzeszutek Wilk
2012-10-23 18:12 ` [PATCH 10/10] xen/pvh: /dev/xen/privcmd changes Konrad Rzeszutek Wilk
2012-10-24 7:13 ` [Xen-devel] [PATCH V5] PVH patches for v3.8 Jan Beulich
2012-10-24 9:34 ` Ian Campbell [this message]
2012-10-24 9:44 ` Jan Beulich
2012-10-24 9:53 ` 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=1351071279.2237.126.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.rathor@oracle.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 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®