From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>, Andi Kleen <ak@muc.de>,
Linus Torvalds <torvalds@osdl.org>, 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 22:24:06 -0800 [thread overview]
Message-ID: <45E7C306.4080400@vmware.com> (raw)
In-Reply-To: <45E79C72.4000806@goop.org>
Jeremy Fitzhardinge wrote:
> Jeremy Fitzhardinge wrote:
>
>> 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?
>>
>>
>
> Something like this (compiled, untested).
>
> J
>
> diff -r 972e84c265cf arch/i386/kernel/paravirt.c
> --- a/arch/i386/kernel/paravirt.c Thu Mar 01 19:12:49 2007 -0800
> +++ b/arch/i386/kernel/paravirt.c Thu Mar 01 19:38:42 2007 -0800
> @@ -32,6 +32,7 @@
> #include <asm/fixmap.h>
> #include <asm/apic.h>
> #include <asm/tlbflush.h>
> +#include <asm/highmem.h>
>
> /* nop stub */
> void _paravirt_nop(void)
> @@ -605,6 +606,8 @@ struct paravirt_ops paravirt_ops = {
>
> .kpte_clear_flush = native_kpte_clear_flush,
>
> + .kmap_atomic_pte = native_kmap_atomic_pte,
> +
>
That doesn't quite work, since we need to know which of the two -
KM_PTE0 or KM_PTE1 is being mapped. But it could be moved to before the
mapping, as you need, and take this as a parameter.
Zach
next prev parent reply other threads:[~2007-03-02 6:24 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
2007-03-02 3:39 ` Jeremy Fitzhardinge
2007-03-02 6:24 ` Zachary Amsden [this message]
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=45E7C306.4080400@vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
/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).