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

Re: [Xen-devel] [v5][PATCH 06/10] hvm_info_table: introduce nr_reserved_device_memory_map



>>> On 04.09.14 at 08:55, <tiejun.chen@xxxxxxxxx> wrote:
> On 2014/9/4 14:32, Jan Beulich wrote:
>>>>> On 04.09.14 at 04:07, <tiejun.chen@xxxxxxxxx> wrote:
>>> On 2014/9/2 16:34, Jan Beulich wrote:
>>>>>>> On 26.08.14 at 13:02, <tiejun.chen@xxxxxxxxx> wrote:
>>>>> --- a/xen/include/public/hvm/hvm_info_table.h
>>>>> +++ b/xen/include/public/hvm/hvm_info_table.h
>>>>> @@ -67,6 +67,9 @@ struct hvm_info_table {
>>>>>
>>>>>        /* Bitmap of which CPUs are online at boot time. */
>>>>>        uint8_t     vcpu_online[(HVM_MAX_VCPUS + 7)/8];
>>>>> +
>>>>> +    /* How many reserved device memory does this domain have? */
>>>>> +    uint32_t    nr_reserved_device_memory_map;
>>>>>    };
>>>>
>>>> This being defacto a private interface between tools and hvmloader
>>>> I wonder if it wouldn't be better to put this before the (in the future)
>>>> eventually growing vcpu_online[].
>>>>
>>>
>>> Any latest consideration? Could we push line above 'uint8_t
>>> vcpu_online[(HVM_MAX_VCPUS + 7)/8];'?
>>>
>>> And I just think it may be reasonable and convenient to expose this info
>>> in hvm_info_table since this is a fixed value that we should record for
>>> all VMs.
>>
>> I think information easily obtained via hypercall doesn't belong here,
> 
> Yes, but just don't feel better to call twice hypercall in hvmloader 
> since this means we have to reallocate memory to store all entries.
> 
> This is a little bit different what we did in libxc since we can't get 
> that number of all entries directly in libxc. But here it may be fine.

Hmm, latching the output of a hypercall here seems even less
reasonable to me. What gets communicated here ought to be
things that have no other good way of telling the VM - at least
that's my understanding of this structure.

>> but I'd also prefer to have input from the tools maintainers here.
>>
> 
> I think I already include all guys by get_maintainer.pc here, but maybe 
> I need ping them actively, so you think who can give us a ack or nack 
> eventually?

People have been traveling a lot lately, so give them a little more
time.

Jan


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.