From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Himanshu Raj <rhim@cc.gatech.edu>
Subject: Re: Regarding page table management changes from Xen v1to Xen v2 (and v3)
Date: Wed, 26 Apr 2006 13:15:25 -0500 [thread overview]
Message-ID: <444FB8BD.4070708@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA486@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> In another example, mmapped access to a file, the new
>> approach will incur these two extra faults for every page
>> fault required to bring a file page to page cache, right?
>>
>
> No, these singleton updates on the Linux demand fault path are issued
> with the update_va_mapping hypercall. This is possible because the
> virtual address that the pte maps is known, so its possible for Xen to
> use a linear pagetable to do the update rather than creating an
> on-demand mapping to the domain's pagetable page. This is an important
> optimization on 32b where Xen address space is tight.
>
Just to make sure I understand, we do the linear mapping for performance
(so we don't have to keep remapping) but not necessarily to save VA
space since the linear mapping uses a fixed amount of space.
Is there any reason that we would strictly require a linear mapping
(other than it being convenient)?
Thanks,
Anthony Liguori
> Ian
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2006-04-26 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 18:04 Regarding page table management changes from Xen v1to Xen v2 (and v3) Ian Pratt
2006-04-26 18:15 ` Anthony Liguori [this message]
2006-04-26 18:13 ` Keir Fraser
2006-04-26 18:19 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2006-04-26 20:49 Nakajima, Jun
2006-04-26 20:00 Ian Pratt
2006-04-26 23:33 ` Anthony Liguori
2006-04-27 8:23 ` Keir Fraser
2006-04-26 17:51 Ian Pratt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=444FB8BD.4070708@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=rhim@cc.gatech.edu \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.