From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: George.Dunlap@eu.citrix.com, xen-devel@lists.xenproject.org,
keir.xen@gmail.com, tim@xen.org, roger.pau@citrix.com
Subject: Re: [V2 PATCH 0/8]: PVH dom0....
Date: Tue, 26 Nov 2013 17:32:46 -0800 [thread overview]
Message-ID: <20131126173246.4765acfb@mantra.us.oracle.com> (raw)
In-Reply-To: <5294E33302000078000A7DDF@nat28.tlf.novell.com>
On Tue, 26 Nov 2013 18:06:43 +0000
"Jan Beulich" <jbeulich@suse.com> wrote:
> >>> George Dunlap <George.Dunlap@eu.citrix.com> 11/26/13 6:21 PM >>>
> >On Mon, Nov 25, 2013 at 11:02 AM, Jan Beulich <JBeulich@suse.com>
> >wrote:
> >>>>> On 25.11.13 at 11:57, Roger Pau Monné<roger.pau@citrix.com>
> >>>>> wrote:
> >>> On 25/11/13 11:49, George Dunlap wrote:
> >>>> * What is the risk that the new interfaces will turn out to be a
> >>>> bad fit or difficult to support going forward?
> >>>
> >>> But I don't think this applies to PVH Dom0, the DomU interface has
> >>> already been marked as experimental, and subject to change. The
> >>> same applies here, Dom0 PVH interface would be considered
> >>> experimental.
> >>
> >> Actually I don't think we were viewing it that way - with 4.4 out,
> >> consumers should be permitted to make use of the interfaces
> >> even if the implementation is still experimental. If we didn't
> >> stick to the interfaces once they're in a release, proper consumers
> >> couldn't appear (i.e. the Linux patch set would not be able to
> >> be pushed into Linus'es tree).
> >
> >Right; but this is an argument against checking it in for 4.4.
> >
> >If Mukesh wants the non-final stuff to be checked into Xen, I think
> >we have to agree not to push the Linux side until it's something we
> >can agree to support.
>
> Actually my earlier comment was meant to be on the DomU side only.
> And I said elsewhere that there's not really any new interface in the
> Dom0 code presented so far, so checking that it wouldn't nail down
> anything that isn't already nailed down due to DomU support.
>
> Jan
Correct, for everything Jan has said in this thread.
Mukesh
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-27 1:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 0:03 [V2 PATCH 0/8]: PVH dom0 Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 1/8] PVH dom0: iommu related changes Mukesh Rathor
2013-11-25 1:19 ` Konrad Rzeszutek Wilk
2013-11-25 8:47 ` Jan Beulich
2013-11-25 8:35 ` Jan Beulich
2013-11-26 14:57 ` George Dunlap
2013-11-23 0:03 ` [V2 PATCH 2/8] PVH dom0: create update_memory_mapping() function Mukesh Rathor
2013-11-25 8:43 ` Jan Beulich
2013-11-25 23:20 ` Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 3/8] PVH dom0: move some pv specific code to static functions Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 4/8] dom0: construct_dom0 changes Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 5/8] PVH dom0: implement XENMEM_add_to_physmap_range for x86 Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 6/8] PVH dom0: Introduce p2m_map_foreign Mukesh Rathor
2013-11-26 16:00 ` George Dunlap
2013-11-26 16:11 ` Ian Campbell
2013-11-26 17:35 ` George Dunlap
2013-11-23 0:03 ` [V2 PATCH 7/8] pvh dom0: Add and remove foreign pages Mukesh Rathor
2013-11-25 9:03 ` Jan Beulich
2013-11-25 19:00 ` Daniel De Graaf
2013-11-26 0:32 ` Mukesh Rathor
2013-11-26 15:03 ` Daniel De Graaf
2013-11-27 1:19 ` Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 8/8] pvh dom0: add opt_dom0pvh to setup.c Mukesh Rathor
2013-11-25 9:04 ` Jan Beulich
2013-11-26 1:18 ` Mukesh Rathor
2013-11-25 9:06 ` [V2 PATCH 0/8]: PVH dom0 Jan Beulich
2013-11-25 10:49 ` George Dunlap
2013-11-25 10:57 ` Roger Pau Monné
2013-11-25 11:02 ` Jan Beulich
2013-11-26 17:20 ` George Dunlap
2013-11-26 18:06 ` Jan Beulich
2013-11-27 1:32 ` Mukesh Rathor [this message]
2013-11-25 11:05 ` Jan Beulich
2013-11-25 11:02 ` Roger Pau Monné
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=20131126173246.4765acfb@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir.xen@gmail.com \
--cc=roger.pau@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).