From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
ebiederm@xmission.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, ijc@hellion.org.uk
Subject: Re: early fixmap causes kmap breakage
Date: Tue, 30 Dec 2008 07:13:44 +0100 [thread overview]
Message-ID: <20081230061344.GA28281@elte.hu> (raw)
In-Reply-To: <20081230040118.GA27679@wotan.suse.de>
* Nick Piggin <npiggin@suse.de> wrote:
> On Mon, Dec 29, 2008 at 03:17:31PM -0800, Andrew Morton wrote:
> > On Thu, 18 Dec 2008 22:15:43 +0100
> > Nick Piggin <npiggin@suse.de> wrote:
> >
> > > Hi,
> > >
> > > I've debugged a problem where i386+pae systems with more than a few CPUs
> > > blow up at boot in the kmap_atomic code.
> >
> > ping?
>
> No further progress here, I'm waiting on input for how to fix this
> "nicely". Meantime, clearing the early fixmap pte I guess works, but you
> lose a page... is it possible to put it into .initdata or is there some
> issue with that? (I guess on a PAE kernel, 4K isn't a big deal).
yeah, 4K shouldnt be a big deal. Mind sending a patch for this?
Ingo
next prev parent reply other threads:[~2008-12-30 6:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 21:15 early fixmap causes kmap breakage Nick Piggin
2008-12-29 23:17 ` Andrew Morton
2008-12-30 4:01 ` Nick Piggin
2008-12-30 6:13 ` Ingo Molnar [this message]
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
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=20081230061344.GA28281@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=ijc@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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