From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH v1 0/8]: PVH (PV guest with extensions)u
Date: Mon, 24 Sep 2012 12:06:40 -0400 [thread overview]
Message-ID: <20120924160640.GA21156@phenom.dumpdata.com> (raw)
In-Reply-To: <20120924152951.GA1458@phenom.dumpdata.com>
On Mon, Sep 24, 2012 at 11:29:51AM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Sep 24, 2012 at 04:16:29PM +0100, Stefano Stabellini wrote:
> > On Fri, 21 Sep 2012, Mukesh Rathor wrote:
> > > Hi guys,
> > >
> > > Ok, I've made all the changes from prev RFC patch submission. Tested
> > > all the combinations. The patches are a bit smaller from before, and
> > > couldn't be separated like before, so I can't state whats different in
> > > each patch. But, it's not too bad to review now.
> > >
> > > As before, they were built on top of
> > > fc6bdb59a501740b28ed3b616641a22c8dc5dd31 from the following tree:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>
> I took them for a spin over the weekend and stuck them on top of my
> #linux-next -
>
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git linux-next-pvh
>
> which worked well as PV guest (dom0, domU, etc). It didn't do too well
> as PVHVM guest, but that might be just that some of the 'if (xen..)'
> are properly not set or I mismerged badly. The later is probably likely as
> I did screw it up at least twice (as you can see from my log).
>
> Hm, let me give them also a whirl on top of fc6bdb59a501740b28ed3b616641a22c8dc5dd31
And with 3683243b2c551e58082b179fd153c7d43ddc503b applied on top of it
I boots just fine. So I had to mess up the merge somehow.
>
> >
> > The patch series is not in a bad state. It is reasonable to aim for a
> > merge in 3.8.
> > At least the xen_remap_domain_mfn_range, ballooning and privcmd changes,
> > which interfaces are going to be shared with Xen on ARM ;-)
next prev parent reply other threads:[~2012-09-24 16:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 19:12 [PATCH v1 0/8]: PVH (PV guest with extensions) Mukesh Rathor
2012-09-24 15:16 ` [PATCH v1 0/8]: PVH (PV guest with extensions)u Stefano Stabellini
2012-09-24 15:23 ` Ian Campbell
2012-09-24 15:29 ` Konrad Rzeszutek Wilk
2012-09-24 16:06 ` Konrad Rzeszutek Wilk [this message]
2012-09-25 13:47 ` [PATCH v1 0/8]: PVH (PV guest with extensions) Ian Campbell
2012-09-25 13:54 ` Ian Campbell
2012-10-01 21:28 ` Mukesh Rathor
2012-10-02 9:35 ` Ian Campbell
2012-10-03 19:11 ` Mukesh Rathor
2012-10-03 20:39 ` Konrad Rzeszutek Wilk
2012-10-04 8:15 ` Ian Campbell
2012-10-04 12:52 ` Konrad Rzeszutek Wilk
2012-10-04 13:12 ` Ian Campbell
2012-10-04 18:23 ` Mukesh Rathor
2012-10-02 13:09 ` Konrad Rzeszutek Wilk
2012-10-02 18:55 ` Mukesh Rathor
2012-10-03 10:24 ` Ian Campbell
2012-10-03 22:26 ` Mukesh Rathor
2012-10-04 8:17 ` Ian Campbell
2012-09-26 13:25 ` Ian Campbell
2012-09-26 13:37 ` Konrad Rzeszutek Wilk
2012-09-26 14:46 ` Konrad Rzeszutek Wilk
2012-09-26 15:21 ` 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=20120924160640.GA21156@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=stefano.stabellini@eu.citrix.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).