From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Lameter <clameter@sgi.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
akpm@linux-foundation.org, ak@suse.de,
linux-kernel@vger.kernel.org, tony.luck@intel.com,
asit.k.mallick@intel.com
Subject: Re: x86_64: potential critical issue with quicklists and page table pages
Date: Tue, 25 Sep 2007 07:27:45 +1000 [thread overview]
Message-ID: <1190669265.6886.69.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.0.999.0709211212130.16478@woody.linux-foundation.org>
On Fri, 2007-09-21 at 12:21 -0700, Linus Torvalds wrote:
> Yeah, and the whole thing seems totally bogus. It totally depends on
> mmu_gather doing everything right (which very much includes the dependency
> on mmu gathering disabling preempt).
>
> For exmaple, if we were to go back to the original small tlb_gather with a
> simple quicklist on the stack, rather than the per-cpu datastructure, the
> quicklists would immediately break horribly - simply because they are
> incorrectly now depending on the internal semantics of that tlb-gather.
>
> As it is, the quicklists try to be something separate, but by virtue of
> being separate, they will always be buggy.
>
> The only way to fix it would be to integrate the quicklist stuff *with*
> the mmu_gather stuff, so that these kinds of implementation issues are
> explicitly shown in the relationship, instead of havign two "independent"
> pieces of code where one piece very subtly depends on the exact
> implementation of the other.
I've been mostly offline since KS (since a bit before in fact), so I
missed some of those discussions but so that you know, I'm toying a bit
with mmu gather and page table accessors at the moment, and one of the
things I've been contemplating is just that ... integrating a quicklist
in the gather to handle just that (and possibly other issues that have
been overlooked on some archs).
I'd suggest just reverting the patch for now (well, I see from the
commit list that you did just that) and I'll try to come up with
something better.
Christoph, I'd be happy if you didn't start butchering mmu_gather just
right now since I'm doing just that and it will collide all over the
place :-) Or if you want something specific done, please throw
ideas/patches at me and I'll integrate that in my serie.
Cheers,
Ben.
next prev parent reply other threads:[~2007-09-24 21:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 18:07 Siddha, Suresh B
2007-09-21 18:18 ` Andi Kleen
2007-09-21 18:48 ` Linus Torvalds
2007-09-21 18:50 ` Christoph Lameter
2007-09-21 18:55 ` Linus Torvalds
2007-09-21 19:05 ` Linus Torvalds
2007-09-21 19:07 ` Christoph Lameter
2007-09-21 19:21 ` Linus Torvalds
2007-09-21 19:26 ` Christoph Lameter
2007-09-21 19:40 ` Linus Torvalds
2007-09-21 19:44 ` Linus Torvalds
2007-09-21 19:56 ` Christoph Lameter
2007-09-21 19:59 ` Luck, Tony
2007-09-21 20:15 ` Christoph Lameter
2007-09-24 21:27 ` Benjamin Herrenschmidt [this message]
2007-09-24 21:42 ` Christoph Lameter
2007-09-25 0:09 ` Benjamin Herrenschmidt
2007-09-21 18:48 ` Christoph Lameter
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=1190669265.6886.69.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=asit.k.mallick@intel.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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®