From: Christopher Warner <chris@servertogo.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: cwarner@kernelcode.com, Andi Kleen <ak@suse.de>,
Dave Jones <davej@redhat.com>, Chris Wright <chrisw@osdl.org>,
"Sergey S. Kostyliov" <rathamahata@ehouse.ru>,
Clem Taylor <clem.taylor@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: x86-64 bad pmds in 2.6.11.6 II
Date: Fri, 29 Apr 2005 07:12:59 -0400 [thread overview]
Message-ID: <1114773179.9543.14.camel@jasmine> (raw)
In-Reply-To: <Pine.LNX.4.61.0504191636570.13422@goblin.wat.veritas.com>
> It does. Well, I needed to restudy exec_mmap and switch_mm in detail,
> and having done so, I agree that the only way you can get through
> exec_mmap's activate_mm without fully flushing the cpu's TLB, is if
> the active_mm matches the newly allocated mm (itself impossible since
> there's a reference on the active_mm), and the cpu bit is still set
> in cpu_vm_mask - precisely not the case if we went through leave_mm.
> Yet I was claiming your leave_mm fix could flush TLB for exec_mmap
> where it wasn't already done.
>
> Sorry for letting the neatness of my pmd/stack story blind me
> to its impossibility, and for wasting your time.
>
> Hugh
> -
Any updated information one should know about this before testing?
I'm getting bad pmds in 2.6.11.5; Tyan S2882/dual AMD 246 opterons. The
problem only occurs when doing some thread intensive task. I'm going to
try and strace/bt and send some information as it occurs. Hardware is
almost identical to the setup above.
-Christopher Warner
next prev parent reply other threads:[~2005-04-29 16:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 21:44 x86-64 bad pmds in 2.6.11.6 Dave Jones
2005-03-31 10:41 ` Andi Kleen
2005-03-31 21:52 ` Dave Jones
2005-04-01 11:52 ` Sergey S. Kostyliov
2005-04-07 2:49 ` Dave Jones
2005-04-07 6:29 ` Andi Kleen
2005-04-14 13:54 ` Hugh Dickins
2005-04-14 17:01 ` Andi Kleen
2005-04-14 17:34 ` Hugh Dickins
2005-04-14 18:10 ` Andi Kleen
2005-04-14 18:11 ` x86-64 bad pmds in 2.6.11.6 II Andi Kleen
2005-04-14 18:27 ` Chris Wright
2005-04-15 17:24 ` Andi Kleen
2005-04-15 17:28 ` Chris Wright
2005-04-15 17:58 ` Hugh Dickins
2005-04-15 18:07 ` Dave Jones
2005-04-22 17:37 ` Debugging patch was " Andi Kleen
2005-04-27 14:23 ` New debugging " Andi Kleen
2005-04-27 17:37 ` Dave Jones
2005-04-29 11:07 ` Hans Kristian Rosbach
2005-04-19 13:35 ` Andi Kleen
2005-04-19 15:52 ` Hugh Dickins
2005-04-29 11:12 ` Christopher Warner [this message]
2005-04-29 16:13 ` Chris Wright
2005-04-29 17:32 ` Dave Jones
2005-05-02 17:00 ` Andi Kleen
2005-05-02 15:28 ` Christopher Warner
2005-05-02 20:33 ` Chris Wright
2005-05-02 21:08 ` Dave Jones
2005-05-03 14:28 ` Andi Kleen
2005-05-03 15:15 ` Dave Jones
2005-05-10 9:36 ` Christopher Warner
2005-05-10 16:26 ` Chris Wright
2005-05-10 12:03 ` Christopher Warner
2005-05-10 16:38 ` Dave Jones
2005-05-10 16:46 ` Andi Kleen
2005-05-10 16:59 ` Dave Jones
2005-05-10 20:32 ` Andi Kleen
2005-05-10 20:43 ` Chris Wright
2005-05-12 21:23 ` Andi Kleen
2005-05-13 21:51 ` Peter J. Stieber
2005-05-14 17:29 ` Peter J. Stieber
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=1114773179.9543.14.camel@jasmine \
--to=chris@servertogo.com \
--cc=ak@suse.de \
--cc=chrisw@osdl.org \
--cc=clem.taylor@gmail.com \
--cc=cwarner@kernelcode.com \
--cc=davej@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@ehouse.ru \
/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