[Xen-ia64-devel] [Patch-resend] Add more dom0 operations

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

Hi, Dan,
        Attached is the updated version to dom0_ops.c. After some
discussion with Ian, we decided to remove newly added hypercall and
instead turn to other means in user application level. Then rest stuff
is all IA64 specific without any touch to common code. Please apply.

Signed-off-by Kevin Tian <Kevin.tian@xxxxxxxxx>

Thanks,
Kevin

>-----Original Message-----
>From: Magenheimer, Dan (HP Labs Fort Collins)
>[mailto:dan.magenheimer@xxxxxx]
>Sent: Wednesday, June 15, 2005 2:58 AM
>To: Tian, Kevin
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Patch] Add more dom0 operations
>
>Kevin ---
>
>I've accepted and pushed to xen-ia64.bkbits.net all of your
>patches except this one.  Since this impacts common code
>in a "temporary" way, I suspect Keir would reject it.
>
>Please start a thread on xen-devel to discuss the right
>way to make dom0_ops.c more friendly for arch-dep features
>and we'll see what Keir and the Xen core maintainers
>think.
>
>> 3. I'm not sure why latest check-in about DOM0_GETMEMLIST differs
much
>> from x86 behavior. Could you explain a bit about that? IMHO, XEN/IA64
>
>I'll leave it to Matt to explain this in more detail.
>
>Thanks,
>Dan
>
>> -----Original Message-----
>> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx]
>> Sent: Tuesday, June 14, 2005 8:07 AM
>> To: Magenheimer, Dan (HP Labs Fort Collins)
>> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: [Patch] Add more dom0 operations
>>
>> Hi, Dan,
>>      This patch adds more dom0 operations support, with following
>> notes:
>>
>> 1. Each architecture may have its own set of operations, so a new
>> dom0_ops_ia64.h is created temporarily. Later cleaner re-org should
be
>> made. :)
>>
>> 2. Add a new hypercall DOM0_GET_SECTIONINFO, to get memory hole,
>I/O
>> port, etc in guest physical address space. This is necessary
>> for CP and
>> DM to create foreign map, especially for VTI domain. As Ian
>> said before,
>> para-virtualized x86 guest is configured with contiguous
>> physical memory
>> without any hole. Though currently not required for para, keeping it
>> there at least provides a possibility for other variations. :)
>>
>> 3. I'm not sure why latest check-in about DOM0_GETMEMLIST differs
much
>> from x86 behavior. Could you explain a bit about that? IMHO, XEN/IA64
>> can have same syntax as x86 easily, since page allocator already
>> aggregates available pages list under domain struct. So a different
>> version is provided enclosed by CONFIG_VTI. If we can set on the same
>> page later, it may be extracted out then.
>>
>> Signed-off-by        Kevin Tian <Kevin.tian@xxxxxxxxx>
>>
>> Thanks,
>> Kevin
>>

Attachment: patch_dom0_ops
Description: patch_dom0_ops

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel