Re: [PATCH v3 03/17] KVM: x86/xen: intercept xen hypercalls if enabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 23 December 2020 08:36:44 GMT, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
>I think all the Xen support code should be conditional on a new config
>option so that normal configs don't have to build the code (and open
>potential attack vectors).

None of this is usable by the guest (as an attack vector or otherwise) unless explicitly enabled by the VMM. And for clock stuff it's even using the *same* functions that are used for native KVM guests, just parameterised a little for the different locations.

I saw the previous discussion but didn't really think it was worth adding yet another build time option for the kernel.

Even when I add event channel support I plan to use the same user_cmpxchg functionality to clean up the KVM steal time handling and even that part won't be Xen-specific.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux