From: Andi Kleen <andi@firstfloor.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: NMI between switch_mm and switch_to
Date: Tue, 28 Jul 2009 11:23:34 +0200 [thread overview]
Message-ID: <87vdldgnzd.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1248767472.6987.2806.camel@twins> (Peter Zijlstra's message of "Tue, 28 Jul 2009 09:51:12 +0200")
Peter Zijlstra <a.p.zijlstra@chello.nl> writes:
> We could use preempt notifiers (or put in our own hooks) to disable
> callchains during the context switch I suppose.
You can simply check if cr3 matches the current->mm page tables
and not dump if they are not.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-07-28 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 4:49 NMI between switch_mm and switch_to Paul Mackerras
2009-07-28 7:51 ` Peter Zijlstra
2009-07-28 9:23 ` Andi Kleen [this message]
2009-08-03 8:29 ` Ingo Molnar
2009-08-03 10:32 ` Paul Mackerras
2009-08-03 10:43 ` Ingo Molnar
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=87vdldgnzd.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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