MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <19001.63708.989256.78908@cargo.ozlabs.ibm.com>
Date: Thu, 18 Jun 2009 18:20:44 +1000
From: Paul Mackerras <paulus@samba.org>
To: Ingo Molnar <mingo@elte.hu>, Peter Zijlstra <a.p.zijlstra@chello.nl>
CC: linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Subject: Accessing user memory from NMI
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1000
Lines: 19

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.

Paul.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/