From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"yinghai@kernel.org" <yinghai@kernel.org>,
"jeremy@goop.org" <jeremy@goop.org>,
"hpa@zytor.com" <hpa@zytor.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen MMU's requirement to pin pages RO and initial_memory_mapping.
Date: Mon, 16 May 2011 14:54:39 -0700 [thread overview]
Message-ID: <4DD19D1F.3070506@linux.intel.com> (raw)
In-Reply-To: <20110516154132.GA12486@dumpdata.com>
On 05/16/2011 08:41 AM, Konrad Rzeszutek Wilk wrote:
>> They become pagetable pages when:
>>
>> - they are explicitly pinned by pin_pagetable_pfn
>>
>> - they are hooked into the current pagetable
>
> Ok, so could we use those two calls to trigger the pagetable walk
> and mark them RO as appropiate? Which call sites are those? The
> xen_set_pgd/xen_set_pud/xen_set_pmd ? Presumarily we don't have
> to do that for the PTE's that are already mapped (as
> xen_setup_kernel_pagetable, and xen_map_identity_early do this
> already).
>
>> Like you wrote, considering that the x86_64 version of
>> kernel_physical_mapping_init hooks the pagetable pages into the
>> currently used pagetable, it wouldn't be possible to mark the pagetable
>> pages RO after init_memory_mapping.
>
Doesn't Xen have some kind of compatibility mode which could be used
during setup?
-hpa
next prev parent reply other threads:[~2011-05-16 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 15:30 Xen MMU's requirement to pin pages RO and initial_memory_mapping Konrad Rzeszutek Wilk
2011-05-16 10:23 ` Stefano Stabellini
2011-05-16 15:41 ` Konrad Rzeszutek Wilk
2011-05-16 21:54 ` H. Peter Anvin [this message]
2011-05-17 17:51 ` Stefano Stabellini
2011-05-17 18:07 ` Konrad Rzeszutek Wilk
2011-05-17 17:50 ` Stefano Stabellini
2011-05-17 18:05 ` Konrad Rzeszutek Wilk
2011-05-17 18:17 ` Konrad Rzeszutek Wilk
2011-05-23 15:20 ` Stefano Stabellini
2011-05-24 13:06 ` Konrad Rzeszutek Wilk
2011-05-24 16:24 ` Stefano Stabellini
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=4DD19D1F.3070506@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yinghai@kernel.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).