From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Don Zickus <dzickus@redhat.com>
Cc: Li Zhong <zhong@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, paulus@samba.org, mingo@elte.hu,
acme@ghostprotocols.net, Vegard Nossum <vegardno@ifi.uio.no>,
tony.luck@intel.com, bp@amd64.org, robert.richter@amd.com,
lenb@kernel.org, minyard@acm.org, wim@iguana.be,
linux-edac@vger.kernel.org, oprofile-list@lists.sf.net,
linux-acpi@vger.kernel.org,
openipmi-developer@lists.sourceforge.net,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 x86 1/2] fix page faults by nmiaction in nmi if kmemcheck is enabled
Date: Mon, 05 Mar 2012 18:55:18 +0100 [thread overview]
Message-ID: <1330970118.11248.256.camel@twins> (raw)
In-Reply-To: <20120305155434.GT3083@redhat.com>
On Mon, 2012-03-05 at 10:54 -0500, Don Zickus wrote:
> This is one way of doing this. I was trying to avoid this when I rewrote the
> nmi handlers, because everyone kept screwing up the structs. I thought it
> would be safer to have callers pass in data based on an api instead.
Apparently kmemcheck marks pages as non-present and does magic in the
fault handler. Having the action thing allocated meant kmemcheck also
marks that thing as non-present in the page-tables, the list iteration
from NMI context would then fault and things would go funny.
There's two ways out, help kmemcheck with a new annotation (which of
course starts with checking if there isn't already such a thing).
Or this one, avoid the action things from being allocated, this
side-steps kmemcheck and avoids the problem thusly.
Sadly this patch doesn't at all mention the first possibility and why
that isn't a feasible approach. A well...
next prev parent reply other threads:[~2012-03-05 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1329717665.3448.28.camel@ThinkPad-T61>
[not found] ` <1329735648.2293.307.camel@twins>
[not found] ` <1329788560.3448.45.camel@ThinkPad-T61>
[not found] ` <1329819437.2293.382.camel@twins>
[not found] ` <1329990828.19165.36.camel@ThinkPad-T61>
[not found] ` <1330340324.11248.60.camel@twins>
2012-03-05 10:05 ` [PATCH v2 x86 1/2] fix page faults by nmiaction in nmi if kmemcheck is enabled Li Zhong
2012-03-05 10:29 ` Wim Van Sebroeck
2012-03-06 1:46 ` Li Zhong
2012-03-05 15:54 ` Don Zickus
2012-03-05 17:55 ` Peter Zijlstra [this message]
2012-03-05 17:49 ` Peter Zijlstra
2012-03-05 21:45 ` Don Zickus
2012-03-06 10:09 ` [PATCH v3 " Li Zhong
2012-03-06 10:27 ` Vegard Nossum
2012-03-09 9:52 ` Li Zhong
2012-03-06 15:00 ` Don Zickus
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=1330970118.11248.256.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=bp@amd64.org \
--cc=dzickus@redhat.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=oprofile-list@lists.sf.net \
--cc=paulus@samba.org \
--cc=robert.richter@amd.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vegardno@ifi.uio.no \
--cc=wim@iguana.be \
--cc=x86@kernel.org \
--cc=zhong@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).