RE: [Xen-ia64-devel] [PATCH] [RFC] [TAKE3] P2M/VP (incomplete) patches

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

>From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx]
>Sent: 2006年3月25日 8:44
>>
>> Do you mean the grant table itself presents as read-only to guest? X86
>> version awards xenlinux to manage allocation/release of grant table
>> entries.
>
>No. I should have been more concrete.
>The current patch ignores GTF_readonly flags.
>It should be supported.
>

I see.

>>
>> IA64 is a bit different as PPC, since xen/ia64 can walk guest virtual
>> address directly while PPC can't. So normally people have two options:
>>
>> - Injected faults into guest when failed, and then let guest re-execute
>> hypercall. Cons is that forward progress may not be ensured when
>> parameter buffer is huge. May need some transient data to track the
>> progress.
>
>A hypercall may require more than one copy_{to, from}_guest().
>In such case just re-executing hypercall doesn't work.
>It is needed for xen to track hypercall progress and to resume
>after injecting faults somehow.

Exactly. hypercall_create_continuation is the template how to restart 
hypercall from a intermediate state.

Thanks,
Kevin

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