From: Andi Kleen <andi@firstfloor.org>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Change x86 Machine check handler to use unlocked_iocl instead of ioctl
Date: Wed, 09 Jan 2008 06:05:28 +0000 [thread overview]
Message-ID: <20080109060528.GA8202@one.firstfloor.org> (raw)
In-Reply-To: <4785B342.2070501@suse.de>
On Thu, Jan 10, 2008 at 11:25:14AM +0530, Nikanth Karthikesan wrote:
> The Machine check handler registers ioctl handler that is called
> with the BKL held. Changing to register unlocked_ioctl instead.
> Also mce ioctl handler does not seem to need any lock protection.
Thanks, but I already did that here on my own.
-Andi
next prev parent reply other threads:[~2008-01-09 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 5:51 [PATCH] Change x86 Machine check handler to use unlocked_iocl instead Nikanth Karthikesan
2008-01-09 6:05 ` Andi Kleen [this message]
2008-01-09 10:20 ` [PATCH] Change x86 Machine check handler to use unlocked_iocl 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=20080109060528.GA8202@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).