From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@suse.de>, "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] x86: fix PSE pagetable construction
Date: Sat, 28 Apr 2007 00:39:22 -0600 [thread overview]
Message-ID: <m1odl9gfz9.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <4632E9F1.8020407@goop.org> (Jeremy Fitzhardinge's message of "Fri, 27 Apr 2007 23:30:09 -0700")
Jeremy Fitzhardinge <jeremy@goop.org> writes:
> I don't have any particularly bright ideas, but there is the other idea
> I mentioned. I could pre-initialize the pagetable with the Xen
> template, but use unconditional calls to set_pte in pagetable_init.
> However, the init-time xen_set_pte simply refuse to set _PAGE_WRITE on a
> pte which isn't already writable, thereby protecting the RO state of the
> pagetable pages. Once pagetable construction has finished, it would
> switch to the real xen_set_pte, which operates as normal.
>
> This has the downside of making init-time xen_set_pte a little strange,
> but it does have the advantage of making the Xen constraints solely the
> responsibility of the Xen code, and it is mitigated by the fact that it
> is only in effect during pagetable_init.
>
> Would that work for everyone?
For a short term solution it sounds reasonable.
Eric
next prev parent reply other threads:[~2007-04-28 6:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 2:15 Jeremy Fitzhardinge
2007-04-28 5:56 ` Eric W. Biederman
2007-04-28 6:30 ` Jeremy Fitzhardinge
2007-04-28 6:39 ` Eric W. Biederman [this message]
2007-04-28 10:29 ` Andi Kleen
2007-04-28 14:28 ` Jeremy Fitzhardinge
2007-04-28 15:27 ` Eric W. Biederman
2007-04-28 23:25 ` Jeremy Fitzhardinge
2007-04-28 17:23 ` Eric W. Biederman
2007-04-28 18:03 ` Andi Kleen
2007-04-28 18:32 ` Eric W. Biederman
2007-04-28 10:25 ` Andi Kleen
2007-04-28 14:30 ` Jeremy Fitzhardinge
2007-04-28 14:55 ` Jeremy Fitzhardinge
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=m1odl9gfz9.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®