From: Thomas Gleixner <tglx@linutronix.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Borislav Petkov <bp@alien8.de>,
Attilio Rao <attilio.rao@citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v4 1/2] XEN/X86: Improve semantic support for x86_init.mapping.pagetable_reserve
Date: Fri, 24 Aug 2012 17:20:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1208241719030.2856@ionos> (raw)
In-Reply-To: <alpine.DEB.2.02.1208241412040.15568@kaball.uk.xensource.com>
On Fri, 24 Aug 2012, Stefano Stabellini wrote:
> On Fri, 24 Aug 2012, Thomas Gleixner wrote:
> > I looked at the whole pgt_buf_* mess and it's amazingly stupid. We
> > could avoid all that dance and make all of that pgt_buf_* stuff static
> > and provide proper accessor functions and hand start, end, top to the
> > reserve function instead of fiddling with global variables all over
> > the place. That'd be a real cleanup and progress.
> >
> > But we can't do that easily. And why? Because XEN is making magic
> > decisions based on those globals in mask_rw_pte().
> >
> > /*
> > * If the new pfn is within the range of the newly allocated
> > * kernel pagetable, and it isn't being mapped into an
> > * early_ioremap fixmap slot as a freshly allocated page, make sure
> > * it is RO.
> > */
> > if (((!is_early_ioremap_ptep(ptep) &&
> > pfn >= pgt_buf_start && pfn < pgt_buf_top)) ||
> > (is_early_ioremap_ptep(ptep) && pfn != (pgt_buf_end - 1)))
> >
> > This comment along with the implementation is really a master piece of
> > obfuscation. Let's see what this is doing. RO is enforced when:
> >
> > This is not an early ioreamp AND
> >
> > pfn >= pgt_buf_start && pfn < pgt_buf_top
> >
> > So why is this checking pgt_buf_top? The early stuff is installed
> > within pgt_buf_start and pgt_buf_end. Anything which is >=
> > pgt_buf_end at this point is completely wrong.
>
> Unfortunately pgt_buf_end only marks the current end of the pagetable
> pages (pgt_buf_end keeps increasing during
> kernel_physical_mapping_init). However at some point
> kernel_physical_mapping_init is going to start mapping the pagetable
> pages themselves, when that happens some of them are not pagetable pages
> yet (pgt_buf_end <= page < pgt_buf_top) but they are going to be in the
> near future.
And how exactly are they allocated between from pgt_buf w/o increasing
pgt_buf_end ?
Thanks,
tglx
next prev parent reply other threads:[~2012-08-24 15:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 15:08 [PATCH v4 0/2] XEN/X86: Document x86_init.mapping.pagetable_reserve and enforce a better semantic Attilio Rao
2012-08-22 15:08 ` [PATCH v4 1/2] XEN/X86: Improve semantic support for x86_init.mapping.pagetable_reserve Attilio Rao
2012-08-23 15:46 ` Thomas Gleixner
2012-08-23 15:44 ` Attilio Rao
2012-08-23 17:14 ` Thomas Gleixner
2012-08-23 17:13 ` Attilio Rao
2012-08-24 10:03 ` Borislav Petkov
2012-08-24 10:10 ` Attilio Rao
2012-08-24 11:36 ` Konrad Rzeszutek Wilk
2012-08-24 11:57 ` Stefano Stabellini
2012-08-24 13:00 ` Thomas Gleixner
2012-08-24 13:24 ` Attilio Rao
2012-08-24 13:45 ` Borislav Petkov
2012-08-24 15:18 ` Thomas Gleixner
2012-08-24 13:32 ` Stefano Stabellini
2012-08-24 15:20 ` Thomas Gleixner [this message]
2012-08-24 17:27 ` Stefano Stabellini
2012-08-24 20:10 ` Thomas Gleixner
2012-08-22 15:08 ` [PATCH v4 2/2] XEN: Document the semantic of x86_init.mapping.pagetable_reserve Attilio Rao
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=alpine.LFD.2.02.1208241719030.2856@ionos \
--to=tglx@linutronix.de \
--cc=attilio.rao@citrix.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=x86@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).