From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: yinghai@kernel.org, jeremy@goop.org,
stefano.stabellini@eu.citrix.com, hpa@zytor.com,
hpa@linux.intel.com, Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: Xen MMU's requirement to pin pages RO and initial_memory_mapping.
Date: Fri, 13 May 2011 11:30:10 -0400 [thread overview]
Message-ID: <20110513153010.GB16519@dumpdata.com> (raw)
aka, remove the hack added by git commit 609cfda586c7fe3e5d1a02c51edb587506294167
(Merge branch 'stable/bug-fixes-for-rc5' of git://git.kernel.org/../xen)
One idea that is on the table was proposed by Yinghai:
"Xen should set RAM for page-table to RO after init_memory mapping."
In other words, don't do the magic 'mask_rw_pte' when set_pte is called.
(and don't do the calls to make_lowmem_page_readonly when allocating
the PTE table, nor PMD, nor PUD) - I think?
But instead do:
a). when we load the cr3? We could go through the whole pagetable and
set the RO as we need?
b). when we are finished with the creation of a page table? So similary
to the point above - don't set the RO on the pages until we have completed
the full creation of the page.
c). when post_allocator_start is called?
d). other ideas?
But I vaguelly recall that we are using the page table as we are adding in the
entries. And that we are pinning them as well. Perhaps the trigger to scan the
pagetable and set them to RO should be done .. at what point? When the PUD/PMD
allocations are done? And when PUD/PMD are set?
next reply other threads:[~2011-05-13 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 15:30 Konrad Rzeszutek Wilk [this message]
2011-05-16 10:23 ` Xen MMU's requirement to pin pages RO and initial_memory_mapping Stefano Stabellini
2011-05-16 15:41 ` Konrad Rzeszutek Wilk
2011-05-16 21:54 ` H. Peter Anvin
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=20110513153010.GB16519@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--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).