From: Ian Campbell <ijc@hellion.org.uk>
To: Nick Piggin <npiggin@suse.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: early fixmap causes kmap breakage
Date: Fri, 09 Jan 2009 10:24:58 +0000 [thread overview]
Message-ID: <1231496698.27350.49.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20081231093356.GD32239@wotan.suse.de>
Adding Jeremy to CC
On Wed, 2008-12-31 at 10:33 +0100, Nick Piggin wrote:
>
> > >> Ditching the swapper_pg_fixmap has some problems.
> > >>
> > >> This appears to break early_printk to a usb debug port, which
> > >> calls set_fixmap_nocache and expects the mapping to last.
> > >>
> > >> This looks like it will have problems with Xen and other
> > >> environments where we come in with a pre-populated page table,
> > >> possibly unmapping something important.
> > >
> > > My patch copies the early fixmap mappings to the new page table.
> > > Isn't this enough?
> >
> > I'm not certain. Xen can get really finicky if you mess with it's
> > pre-established mappings. Which is one of the reasons why we
> > preserve the current mappings. It was a real struggle to find a
> > solution that worked for everything last time we had a PAE problem,
> > and apparently we failed to test with large numbers of cpus in the
> > config.
> >
> > So please excuse me if I'm leery of a quick fix, to code that is
> > obviously insufficiently clean to do what needs to be done
> > intentionally.
>
> Well we should just ask the Xen people whether it will work or not.
> Why wouldn't it? Xen has to be able to cope with kernel mappings
> coming and going.
I think it should be fine from Xen's PoV since one_page_table_init()
correctly uses paravirt_alloc_pte() and set_pte() does the right thing
under Xen.
BTW, I needed this fixlet since set_pte takes a pte_t not a pteval_t,
otherwise:
CC arch/x86/mm/init_32.o
[...]arch/x86/mm/init_32.c: In function 'page_table_range_init':
[...]arch/x86/mm/init_32.c:188: error: incompatible type for argument 2 of 'set_pte'
diff -r cf59aba1694f arch/x86/mm/init_32.c
--- a/arch/x86/mm/init_32.c Fri Jan 09 10:13:31 2009 +0000
+++ b/arch/x86/mm/init_32.c Fri Jan 09 10:16:38 2009 +0000
@@ -185,7 +185,7 @@
newpte = one_page_table_init(pmd);
BUG_ON(lastpte + PTRS_PER_PTE != newpte);
for (i = 0; i < PTRS_PER_PTE; i++) {
- set_pte(newpte + i, pte_val(*(pte + i)));
+ set_pte(newpte + i, *(pte + i));
}
pte = lastpte;
}
--
Ian Campbell
Current Noise: Firebird - Needle In The Groove
"Now we'll have to kill you."
-- Linus Torvalds
next prev parent reply other threads:[~2009-01-09 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 21:15 Nick Piggin
2008-12-29 23:17 ` Andrew Morton
2008-12-30 4:01 ` Nick Piggin
2008-12-30 6:13 ` Ingo Molnar
2008-12-30 7:54 ` Nick Piggin
2008-12-30 8:14 ` Nick Piggin
2008-12-30 10:28 ` Nick Piggin
2008-12-30 22:41 ` Eric W. Biederman
2008-12-31 1:54 ` Nick Piggin
2008-12-31 9:01 ` Eric W. Biederman
2008-12-31 9:33 ` Nick Piggin
2009-01-09 10:24 ` Ian Campbell [this message]
2008-12-30 6:22 ` Eric W. Biederman
2008-12-30 6:35 ` Nick Piggin
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=1231496698.27350.49.camel@zakaz.uk.xensource.com \
--to=ijc@hellion.org.uk \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=tglx@linutronix.de \
/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®