|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] [patch] more correct pfn_valid()
>-----Original Message-----
>From: Ian Pratt [mailto:m+Ian.Pratt@xxxxxxxxxxxx]
>Sent: Thursday, May 19, 2005 5:37 PM
>
>
>
>> OK, got it. Then, aside from para-virtualized linux, do you
>> agree that some change should be made to unmodified vmx
>> domain build and DM? When domain creation in CP and when DM
>> services other domain, they shouldn't operate DomN's memory
>> by simply acquiring a plain continuous page_array which has
>> no hole information. Either extra information about hole, or
>> the page_array itself containing hole, should be added thereafter...
>
>vmx domains already have a virtually mapped pfn->mfn table stored
within
>Xen.
>See phys_to_machine_mapping(gpfn)
>
>Ian
Yes, as you said earlier. But it's not used by CP and DM by far, which
still go to page_array style. :( I just mean some change may be required
there for CP and DM to correctly manipulate other domain's memory.
Thanks,
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- RE: [Xen-devel] [patch] more correct pfn_valid(), (continued)
- RE: [Xen-devel] [patch] more correct pfn_valid(), Tian, Kevin
- RE: [Xen-devel] [patch] more correct pfn_valid(), Tian, Kevin
- RE: [Xen-devel] [patch] more correct pfn_valid(), Ian Pratt
- RE: [Xen-devel] [patch] more correct pfn_valid(), Tian, Kevin
- RE: [Xen-devel] [patch] more correct pfn_valid(), Ian Pratt
- RE: [Xen-devel] [patch] more correct pfn_valid(), Tian, Kevin
- RE: [Xen-devel] [patch] more correct pfn_valid(), Tian, Kevin
- RE: [Xen-devel] [patch] more correct pfn_valid(), Ian Pratt
- RE: [Xen-devel] [patch] more correct pfn_valid(), Dong, Eddie
- RE: [Xen-devel] [patch] more correct pfn_valid(),
Tian, Kevin <=
|
|
|
|
|