From: ykzhao <yakui.zhao@intel.com>
To: Dave Jones <davej@redhat.com>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [Patch] CPUFREQ: Add the suspend/resume flag to avoid smp_call in cpufreq_suspend/resume
Date: Tue, 28 Jul 2009 09:40:12 +0800 [thread overview]
Message-ID: <1248745212.3556.74.camel@localhost.localdomain> (raw)
In-Reply-To: <20090724014918.GA8854@redhat.com>
On Fri, 2009-07-24 at 09:49 +0800, Dave Jones wrote:
> On Fri, Jul 24, 2009 at 09:37:43AM +0800, ykzhao wrote:
> > Subject: [CPUFREQ]: Add the suspend/resume flag to avoid smp_call in cpufreq_suspend/resume
> > From: Zhao Yakui <yakui.zhao@intel.com>
> >
> > Only CPU0 is available in course of cpufreq_suspend/resume.
> > So it is unnecessary to do the smp_call for getting the current
> > cpufreq.
> >
> > Add a flag of suspend/resume to avoid the smp_call in course of
> > cpufreq_suspend/resume.
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=13781
> > http://bugzilla.kernel.org/show_bug.cgi?id=13269
> >
> > Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
> > Tested-by: Christian Casteyde<casteyde.christian@free.fr>
>
> All this goes away if we just made that suspend/resume code
> conditional on powerpc as previously discussed.
Hi, Dave
Will you please point out what we should do to fix the issue son x86
similar to that on powerpc?
Is the patch mentioned already shipped in upstream kernel?
thanks.
>
> We don't need any of it on x86 afaict
>
> Dave
prev parent reply other threads:[~2009-07-28 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 1:37 [Patch] CPUFREQ: Add the suspend/resume flag to avoid smp_call in cpufreq_suspend/resume ykzhao
2009-07-24 1:49 ` Dave Jones
2009-07-24 5:18 ` ykzhao
2009-07-28 1:40 ` ykzhao [this message]
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=1248745212.3556.74.camel@localhost.localdomain \
--to=yakui.zhao@intel.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=linux-acpi@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