Re: [RFC PATCH 0/3] generic hypercall support

Gregory Haskins
2009-05-05T14:21:39Z

[-- Attachment #1: Type: text/plain, Size: 729 bytes --]

Gregory Haskins wrote:
> So rather than allocate a top-level vector, I will add "KVM_HC_DYNAMIC"
> to kvm_para.h, and I will change the interface to follow suit (something
> like s/hypercall/dynhc). Sound good?
>

A small ramification of this change will be that I will need to do
something like add a feature-bit to cpuid for detecting if HC_DYNAMIC is
supported on the backend or not. The current v1 design doesn't suffer
from this requirement because the presence of the dynamic vector itself
is enough to know its supported. I like Avi's proposal enough to say
that its worth this minor inconvenience, but FYI I will have to
additionally submit a userspace patch for v2 if we go this route.

-Greg

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]