From: Tejun Heo <tj@kernel.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, apm: Make on_cpu0() use workqueue instead of work_on_cpu()
Date: Mon, 17 Sep 2012 14:38:29 -0700 [thread overview]
Message-ID: <20120917213829.GN18677@google.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1208281557000.22447@pobox.suse.cz>
On Tue, Aug 28, 2012 at 03:57:27PM -0700, Jiri Kosina wrote:
> On Thu, 23 Aug 2012, Tejun Heo wrote:
>
> > Make APM schedule a work item on CPU0 instead of using the expensive
> > work_on_cpu(); hopefully, this is the last user of work_on_cpu() and
> > we can take out work_on_cpu() in not too distant future.
> >
> > Tested both paths. Seems to work fine.
>
> Applying to apm.git, thanks Tejun.
It seems we need work_on_cpu() after all and I'm planning on
reimplementing it in saner way. Can you please drop this one?
Thanks.
--
tejun
next prev parent reply other threads:[~2012-09-17 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 1:11 [PATCH] x86, apm: Make on_cpu0() use workqueue instead of work_on_cpu() Tejun Heo
2012-08-28 22:57 ` Jiri Kosina
2012-09-17 21:38 ` Tejun Heo [this message]
2012-09-18 10:19 ` Jiri Kosina
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=20120917213829.GN18677@google.com \
--to=tj@kernel.org \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.