From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: roger.pau@citrix.com, jinsong.liu@intel.com,
xen-devel <xen-devel@lists.xen.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] Patches for v3.9 for the Linux kernel.
Date: Fri, 15 Feb 2013 12:39:04 -0500 [thread overview]
Message-ID: <20130215173904.GC10133@phenom.dumpdata.com> (raw)
In-Reply-To: <511E761402000078000BEDD8@nat28.tlf.novell.com>
On Fri, Feb 15, 2013 at 04:53:24PM +0000, Jan Beulich wrote:
> >>> On 15.02.13 at 17:34, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > I know that the PVH patches are not in the Xen tree. I am hoping that
> > at least the hypercalls _are_ OK with everybody so we can continue on
> > with this.
>
> Please don't commit to anything that isn't in the hypervisor tree
> yet. IOW I'd like you to not push the PVH bits that use
> uncommitted hypervisor interfaces (anything preparatory of
> course is okay).
Hm, I believe the only one that was of contention was the 'PHYSDEVOP_map_iomem'
which Mukesh reverted.
The other one is the XENMEM_add_to_physmap_range, which Ian has for ARM.
That is the git commit b6eafa71fa87f4c831e9c2eac736e8ac20b3ea1c
in stable/pvh.v7 tree.
Oh, there is one change in this git commit b8724d6bd1c09e34b6c76b57d07ea4d3fbd8ed4c
..and that gets reverted in 68c5bb99d8b8abbf70b3380bed8eca69648193f5 (by Ian).
So from a hypercall perspective - Ian, is the XENMEM_add_to_physmap_range fully
baked ?
prev parent reply other threads:[~2013-02-15 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 16:34 Konrad Rzeszutek Wilk
2013-02-15 16:53 ` [Xen-devel] " Jan Beulich
2013-02-15 17:39 ` Konrad Rzeszutek Wilk [this message]
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=20130215173904.GC10133@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=jinsong.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.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®