From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Paul Mackerras <paulus@samba.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Subject: Re: Accessing user memory from NMI
Date: Thu, 18 Jun 2009 10:36:09 +0200 [thread overview]
Message-ID: <1245314169.13761.23121.camel@twins> (raw)
In-Reply-To: <19001.63708.989256.78908@cargo.ozlabs.ibm.com>
On Thu, 2009-06-18 at 18:20 +1000, Paul Mackerras wrote:
> What was the conclusion you guys came to about doing a user stack
> backtrace in an NMI handler? Are you going to access user memory
> directly or are you going to use the __fast_get_user_pages approach?
>
> Ben H and I were talking today about what we'd need in order to be
> able to read user memory in a PMU interrupt handler. It looks like we
> could read user memory directly with a bit of care, on 64-bit at
> least. Because of the MMU hash table that would almost always work
> provided the page has already been touched (which stack pages would
> have been), but there is a small chance that the access might fail
> even if the address has a valid PTE. At that point we could fall back
> to the __fast_get_user_pages method, but I'm not sure it's worth it.
Currently we have the GUP based approach, but Ingo is thikning about
making the pagefault handler NMI safe on x86 for .32.
next prev parent reply other threads:[~2009-06-18 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 8:20 Accessing user memory from NMI Paul Mackerras
2009-06-18 8:36 ` Peter Zijlstra [this message]
2009-06-20 16:34 ` Ingo Molnar
2009-06-20 16:58 ` Mathieu Desnoyers
2009-06-20 17:40 ` 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=1245314169.13761.23121.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=benh@kernel.crashing.org \
--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