RE: [Xen-devel] [patch] more correct pfn_valid()

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

 > For this part, I made a mistake to confuse domN and dom0. OK, 
> for paravirtualized guest, there's actually no I/O range for 
> domN, since the front driver in domN will do all things to 
> communicate with backend in Dom0. But what about a driver 
> domain which has access to physical device, thus need real 
> I/O address?

This works the same in dom0 and other domains:
IO machine addresses must be mapped into the kernel virtual address
space before you can use them. They are totally orthogonal to ram
addresses, and don't get mfn->pfn translated.

Ian

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