very very thanks Bryan :-)
#I've tried to find a answer of this question for a week.
>> Now, I'm succeeded read and writing almost of the memory. But
>> It fails when I try to access top 1M region and some bit regions.
>> To be precise, xc_map_foreign_range() of libxc returns error code 14.
>>
>
> This is where Xen locates itself. So that would explain why it is not
> letting you map it. The rest of the guest memory should be laid out
> as you would expect for whatever operating system you are looking at.
>
>
Though I mean pseudo physical memory, this answer is correct?
#I know xen is replaced on virtual address space of DomU.
Ok. If your answer is what I intended, top 1M region problem is solved.
But there are some bit regions I can't access. What are they?
#some regions can't be accessed continuously and some regions can't be
accessed often.
#incidentally, I access to domU while it being paused.
<javascript:goWordLink("incidentally")>
>> #and , Can I get a document about memory allocation of dom0 and DomU
>> somewhere?
>>
>
> I'm not sure if I understand this question. If you are curious about
> how Xen allocates the memory, then I don't know of any good
> documentation on that. If you are curious about how the guest OS uses
> its memory, then you can check out a reference book about the
> operating system (e.g., Windows Internals or Understanding the Linux
> Kernel).
>
>
I meant the former.
thank you for your suggestion :-)
regards.
****************************************
HPCS lab
4th grade student of Colledge of Information Science, University of Tsukuba
Ryo Kanbayashi
|
