[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d5fb841-26be-4ce1-b549-eb7f17f88e61@default>
Date: Fri, 2 Jul 2010 09:08:43 -0700 (PDT)
From: Dan Magenheimer <dan.magenheimer@...cle.com>
To: Stefano Stabellini <stefano.stabellini@...citrix.com>
Cc: Fitzhardinge <jeremy@...p.org>, xen-devel@...ts.xensource.com,
Konrad Wilk <konrad.wilk@...cle.com>,
Jeremy@...inet12.oracle.com, linux-kernel@...r.kernel.org,
Don Dutile <ddutile@...hat.com>,
Sheng Yang <sheng@...ux.intel.com>
Subject: RE: [Xen-devel] Re: [PATCH 0/12] PV on HVM Xen
> From: Stefano Stabellini [mailto:stefano.stabellini@...citrix.com]
>
> On Thu, 1 Jul 2010, Dan Magenheimer wrote:
> > Hi Stefano --
> >
> > What versions of Xen are compatible with this series?
> > I.e. is 4.0 required? Are all Xen-side changes in
> > official 4.0.0? Or only in 4.0-testing (and therefore
> > will be in 4.0.1)? Or only in xen-unstable?
> >
> > If post-4.0.0 xen changes are necessary, could you point
> > out the changesets?
>
> Any Xen version is going to work, but you need unstable to get all the
> features.
>
> In particular you need these patches:
>
> - 21647: implement HVMOP_pagetable_dying
>
> - 21493: update_runstate_area for 32 bit PV on HVM guests
>
> - 21449: implement vector callback for evtchn delivery
>
> - 21445: TSC handling cleanups (version 2)
>
> - 21341: Export timer hypercalls to HVM guests too
>
> - 21339: TSC handling cleanups
Thanks for the thorough reply! Any reason that any of these
cannot or should not be back-ported to go into 4.0.1?
Thanks,
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists