[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <50f4d2ff-3028-990c-b9c9-f85ad2a3c7e9@suse.com>
Date: Mon, 15 May 2017 16:24:24 +0200
From: Juergen Gross <jgross@...e.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>
Cc: Rusty Russell <rusty@...tcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
virtualization@...ts.linux-foundation.org,
xen-devel <xen-devel@...ts.xenproject.org>,
lguest@...ts.ozlabs.org
Subject: Re: Support of lguest?
On 15/05/17 16:22, Vitaly Kuznetsov wrote:
> Juergen Gross <jgross@...e.com> writes:
>
>> Lguest and Xen pv-guests are the only users of pv_mmu_ops (with the
>> one exception of the .exit_mmap member, which is being used by Xen
>> HVM-guests, too).
>>
>> As it is possible now to build a kernel without Xen pv-guest support
>> while keeping PVH and PVHVM support, I thought about putting most
>> pv_mmu_ops functions in #ifdef CONFIG_XEN_HAS_PVMMU sections.
>
> There is an ongoing work to enable PV TLB flushing for Hyper-V guests:
> http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2017-April/104411.html
>
> it utilizes .flush_tlb_others member in pv_mmu_ops.
>
> hopefully, this work will be merged in 4.13.
Thanks for the information. I'll keep .flush_tlb_others member outside
the #ifdef section.
Juergen
Powered by blists - more mailing lists