RE: [Xen-ia64-devel] domU address space

["Dong, Eddie" <eddie.dong@xxxxxxxxx>]

Do we have checks when inserting guest TLB for PV dom? Seems not, 
If a guest insert a TLB with HV VA in domU, the TLB in machine side
may be mis-used by HV. It should be able to be fixed :)
Eddie

Kouya Shimura wrote:
> In addition, It seems that PV domain can use an unimplemented VA
> address except xen area. 
> Ideally xen should check it and reflect the unimplemented address
> fault to the guest. But it sounds overkill. 
> 
> Isaku Yamahata writes:
>> On Thu, Jan 24, 2008 at 09:28:39AM +0800, Dong, Eddie wrote:
>>> Alex & All:
>>>     First of all, pls forgive me that I was out of Xen/IA64 for quit
a
>>> long time, and I didn't fully catch up yet now.
>>>     In the very beginning day of Xen/IA64, I remembered the address
>>> isolation between guest (domU) & hypervisor is not solved though
>>> guest PAL can provide less number of VA bits, it just assume pv
>>> guest won't touch hypervisor address space, i.e. it will strictly
>>> follow PAL reported VA address bits. Is this solved now?
>> 
>> Yes. (Possibly there might be bugs, though.) In paravirtualized
>> domain case, PV domain is running under ring 2 (or ring 1 depending
>> on the compile time configuration), and the xen area is proteceted
>> by privileged level. In VTi domain case, it's protected by psr.vm =
>> 1. 
>> 
>> --
>> yamahata
>> 
>> _______________________________________________
>> Xen-ia64-devel mailing list
>> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-ia64-devel


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