Re: [Xen-devel] [PATCH RFC 1/7] xen/vnuma: subop hypercall and vnuma topology structures.

[Elena Ufimtseva <ufimtseva@xxxxxxxxx>]

Matt
This is for xen only to set the vnuma topology.
Guest will not have this, but will have some other interface to
retreive this info (as we were discussing this in numa aware
ballooning).

Elena

On Wed, Aug 28, 2013 at 12:42 PM, Matt Wilson <msw@xxxxxxxxxx> wrote:
> On Tue, Aug 27, 2013 at 03:54:20AM -0400, Elena Ufimtseva wrote:
>> Defines XENMEM subop hypercall for PV vNUMA enabled guests and provides
>> vNUMA topology information from per-domain vnuma topology build info.
>> TODO:
>> subop XENMEM hypercall is subject to change to sysctl subop.
>>
>> Signed-off-by: Elena Ufimtseva <ufimtseva@xxxxxxxxx>
>
> [...]
>
>> diff --git a/xen/include/xen/domain.h b/xen/include/xen/domain.h
>> index a057069..3d39218 100644
>> --- a/xen/include/xen/domain.h
>> +++ b/xen/include/xen/domain.h
>> @@ -4,6 +4,7 @@
>>
>>  #include <public/xen.h>
>>  #include <asm/domain.h>
>> +#include <public/vnuma.h>
>>
>>  typedef union {
>>      struct vcpu_guest_context *nat;
>> @@ -89,4 +90,12 @@ extern unsigned int xen_processor_pmbits;
>>
>>  extern bool_t opt_dom0_vcpus_pin;
>>
>> +struct domain_vnuma_info {
>> +    uint16_t nr_vnodes;
>> +    int *vdistance;
>> +    vnuma_memblk_t *vnuma_memblks;
>> +    int *vcpu_to_vnode;
>> +    int *vnode_to_pnode;
>
> What's the purpose of providing a vNode to pNode mapping to the guest?
> Or am I misunderstanding that this wouldn't be provided to the guest?
>
>> +};
>> +
>>  #endif /* __XEN_DOMAIN_H__ */
>
> --msw



-- 
Elena

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel