From: "Kevin Winchester" <kjwinchester@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Switch apm to unlocked_kernel
Date: Fri, 23 May 2008 08:36:10 -0300 [thread overview]
Message-ID: <d1af83620805230436w28274e82tc98261b69ecd1330@mail.gmail.com> (raw)
In-Reply-To: <20080522212204.177410b8@core>
On Thu, May 22, 2008 at 5:22 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> This pushes the lock a fair way down and the final kill looks like it
> should be an easy project for someone who wants to have a shot at it.
>
I would like to have a shot at this if no one else if currently
working on it. This would be my first attempt to graduate from
testing (and a few simple patches) to an actual functional change. I
would expect that the steps involved are:
- See what data is affected under the BKL
- See where else that data may be affected (including possible
parallel calls to the same path)
- Decide what locking is necessary
- Implement it (the easy part)
If this is about right (and I'm not missing anything major) - I will
give it a try and see where I get.
If, however, I have just proved that I do not have a full grasp of the
problem, or if someone else is already working on this particular path
- please let me know.
--
Kevin Winchester
next prev parent reply other threads:[~2008-05-23 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 20:22 Alan Cox
2008-05-23 1:03 ` Stephen Rothwell
2008-05-23 11:06 ` Alan Cox
2008-05-23 13:23 ` Stephen Rothwell
2008-05-23 17:25 ` Andrew Morton
2008-05-23 11:36 ` Kevin Winchester [this message]
2008-05-24 18:59 ` [RFC] " Kevin Winchester
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=d1af83620805230436w28274e82tc98261b69ecd1330@mail.gmail.com \
--to=kjwinchester@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®