* When does Xen build 1:1 direct mapping of all physical memory ?
@ 2013-02-25 19:51 Xinxin Jin
2013-02-26 8:31 ` Jan Beulich
0 siblings, 1 reply; 4+ messages in thread
From: Xinxin Jin @ 2013-02-25 19:51 UTC (permalink / raw)
To: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 231 bytes --]
Hi, all,
I assumed that Xen fills up the page table entires for 1:1 direct mapping
of all physical memory at start time, but I cannot find the code. Could
anyone tell me when Xen builds up pte for this mapping ?
Thanks,
--
Xinxin
[-- Attachment #1.2: Type: text/html, Size: 272 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: When does Xen build 1:1 direct mapping of all physical memory ?
2013-02-25 19:51 When does Xen build 1:1 direct mapping of all physical memory ? Xinxin Jin
@ 2013-02-26 8:31 ` Jan Beulich
2013-02-26 22:23 ` Xinxin Jin
0 siblings, 1 reply; 4+ messages in thread
From: Jan Beulich @ 2013-02-26 8:31 UTC (permalink / raw)
To: Xinxin Jin; +Cc: Xen-devel
>>> On 25.02.13 at 20:51, Xinxin Jin <xinxinjin89@gmail.com> wrote:
> I assumed that Xen fills up the page table entires for 1:1 direct mapping
> of all physical memory at start time, but I cannot find the code. Could
> anyone tell me when Xen builds up pte for this mapping ?
xen/arch/x86/mm.c:init_frametable()
Jan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: When does Xen build 1:1 direct mapping of all physical memory ?
2013-02-26 8:31 ` Jan Beulich
@ 2013-02-26 22:23 ` Xinxin Jin
2013-02-27 7:37 ` Jan Beulich
0 siblings, 1 reply; 4+ messages in thread
From: Xinxin Jin @ 2013-02-26 22:23 UTC (permalink / raw)
To: Jan Beulich; +Cc: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 664 bytes --]
Hi Jan, I think init_frametable() is to initialize frame table, whose
virtual address starts at FRAMETABLE_VIRT_START ? How about the direct 1:1
mapping of all of machine memroy whose virtual address start at
DIRECTMAP_VIRT_START?
Thanks,
On Tue, Feb 26, 2013 at 12:31 AM, Jan Beulich <JBeulich@suse.com> wrote:
> >>> On 25.02.13 at 20:51, Xinxin Jin <xinxinjin89@gmail.com> wrote:
> > I assumed that Xen fills up the page table entires for 1:1 direct mapping
> > of all physical memory at start time, but I cannot find the code. Could
> > anyone tell me when Xen builds up pte for this mapping ?
>
> xen/arch/x86/mm.c:init_frametable()
>
> Jan
>
>
--
Xinxin
[-- Attachment #1.2: Type: text/html, Size: 1129 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: When does Xen build 1:1 direct mapping of all physical memory ?
2013-02-26 22:23 ` Xinxin Jin
@ 2013-02-27 7:37 ` Jan Beulich
0 siblings, 0 replies; 4+ messages in thread
From: Jan Beulich @ 2013-02-27 7:37 UTC (permalink / raw)
To: Xinxin Jin; +Cc: Xen-devel
>>> On 26.02.13 at 23:23, Xinxin Jin <xinxinjin89@gmail.com> wrote:
> Hi Jan, I think init_frametable() is to initialize frame table, whose
> virtual address starts at FRAMETABLE_VIRT_START ? How about the direct 1:1
> mapping of all of machine memroy whose virtual address start at
> DIRECTMAP_VIRT_START?
Oh, sorry, yes, this isn't the direct mapping.
Check the calls to map_pages_to_xen() in __start_xen() for the
direct mapping.
Jan
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-02-27 7:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-25 19:51 When does Xen build 1:1 direct mapping of all physical memory ? Xinxin Jin
2013-02-26 8:31 ` Jan Beulich
2013-02-26 22:23 ` Xinxin Jin
2013-02-27 7:37 ` Jan Beulich
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.