[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] x86: re-enable VCPUOP_register_vcpu_time_memory_area
On Thu, May 16, 2013 at 04:01:33PM +0100, Jan Beulich wrote: > >>> On 16.05.13 at 16:40, Ian Campbell <ian.campbell@xxxxxxxxxx> wrote: > > On Thu, 2013-05-16 at 09:47 +0100, Jan Beulich wrote: > >> Regardless of the code freeze I'd still like to propose this for > >> inclusion in 4.3, mainly based on the fact that this got disabled late > >> in the 4.0 release cycle with the expectation that it would get > >> re-enabled soon after. Now that upstream Linux also has, as of 3.8 at > >> least on x86-64, the necessary hypervisor independent support code, it > >> would be odd to not leverage this on Xen. > > > > I went looking for a call to VCPUOP_register_vcpu_time_memory_area in > > 3.10-rc1 and can't find it -- what have I missed? > > The words "hypervisor independent" in my explanation. Iirc Jeremy > had a patch, and the non-Xen pieces got extracted from it for KVM > (in 3.8 I think). The Xen parts would need to be recovered and > pushed upstream. The way I did this for our kernel isn't even coming > close to what would be needed for upstreaming. Does this look like the right bit of old code? https://lkml.org/lkml/2009/10/5/391 --msw _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |