From: Wei Wang <wei.w.wang@intel.com>
To: xen-devel@lists.xen.org, jbeulich@suse.com
Cc: andrew.cooper3@citrix.com, Wei Wang <wei.w.wang@intel.com>
Subject: [PATCH v3 05/11] x86/intel_pstate: avoid calling cpufreq_add_cpu() twice
Date: Thu, 11 Jun 2015 16:27:32 +0800 [thread overview]
Message-ID: <1434011252-17173-1-git-send-email-wei.w.wang@intel.com> (raw)
cpufreq_add_cpu() is already called in the hypercall code path
(the bottom of set_px_pminfo() and inside cpufreq_cpu_init()).
So, we remove the redundant calling here.
Signed-off-by: Wei Wang <wei.w.wang@intel.com>
---
xen/drivers/cpufreq/cpufreq.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/xen/drivers/cpufreq/cpufreq.c b/xen/drivers/cpufreq/cpufreq.c
index 7d186db..6003a8c 100644
--- a/xen/drivers/cpufreq/cpufreq.c
+++ b/xen/drivers/cpufreq/cpufreq.c
@@ -632,8 +632,6 @@ static struct notifier_block cpu_nfb = {
int cpufreq_register_driver(struct cpufreq_driver *driver_data)
{
- void *cpu = (void *)(long)smp_processor_id();
- cpu_callback(&cpu_nfb, CPU_ONLINE, cpu);
if (!driver_data || !driver_data->init
|| !driver_data->verify || !driver_data->exit
|| (!driver_data->target == !driver_data->setpolicy))
--
1.9.1
reply other threads:[~2015-06-11 8:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1434011252-17173-1-git-send-email-wei.w.wang@intel.com \
--to=wei.w.wang@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xen.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.