From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Andi Kleen <ak@muc.de>, Linus Torvalds <torvalds@osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>, Dan Hecht <dhecht@vmware.com>,
Dan Arai <arai@vmware.com>, Andrew Morton <akpm@osdl.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/9] Vmi fix highpte
Date: Thu, 01 Mar 2007 19:08:25 -0800 [thread overview]
Message-ID: <45E79529.9000305@goop.org> (raw)
In-Reply-To: <200703020254.l222smBB009668@zach-dev.vmware.com>
Zachary Amsden wrote:
> Provide a PT map hook for HIGHPTE kernels to designate where they are mapping
> page tables. This information is required so the physical address of PTE
> updates can be determined; otherwise, the mm layer would have to carry the
> physical address all the way to each PTE modification callsite, which is
> even more hideous that the macros required to provide the proper hooks.
>
> So lets not mess up arch neutral code to achieve this, but keep the horror
> in an #ifdef HIGHPTE in include/asm-i386/pgtable.h. I had to use macros
> here because some types are not yet defined in all the include paths for
> this header.
>
> This patch is absolutely required for HIGHPTE kernels to operate properly
> with VMI.
>
Hm, I don't think this interface will work for Xen. In Xen, whenever a
pagetable page gets mapped, it must be mapped RO. map_pt_hook gets
called after the mapping has already been created, so its too late for Xen.
I was planning on adding kmap_atomic_pte() for use in pte_offset_map*(),
which would be wired through to paravirt_ops to allow Xen to make this a
RO mapping. Would this be sufficient for you to do your vmi thing?
J
next prev parent reply other threads:[~2007-03-02 3:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 2:54 [PATCH 4/9] Vmi fix highpte Zachary Amsden
2007-03-02 3:08 ` Jeremy Fitzhardinge [this message]
2007-03-02 3:39 ` Jeremy Fitzhardinge
2007-03-02 6:24 ` Zachary Amsden
2007-03-02 6:29 ` Jeremy Fitzhardinge
2007-03-02 6:31 ` Zachary Amsden
2007-03-02 6:45 ` Jeremy Fitzhardinge
2007-03-02 9:53 ` Zachary Amsden
2007-03-02 16:55 ` Jeremy Fitzhardinge
2007-03-03 7:17 ` Zachary Amsden
2007-03-03 7:43 ` Jeremy Fitzhardinge
2007-03-03 7:58 ` Zachary Amsden
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=45E79529.9000305@goop.org \
--to=jeremy@goop.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=arai@vmware.com \
--cc=chrisw@sous-sol.org \
--cc=dhecht@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).