From: Andy Lutomirski <luto@kernel.org>
To: len.brown@intel.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 2/4] intel_idle: Remove a broadcast MSR fixup at boot
Date: Sun, 13 Mar 2016 21:48:11 -0700 [thread overview]
Message-ID: <7eb5c15595171811aa948480ee51b29fa15fd9b8.1457930807.git.luto@kernel.org> (raw)
In-Reply-To: <cover.1457930807.git.luto@kernel.org>
In-Reply-To: <cover.1457930807.git.luto@kernel.org>
intel_idle already fixes MSRs on each CPU when it registers for that
CPU, so it doesn't need to separately broadcast to all CPUs on
startup.
Signed-off-by: Andy Lutomirski <luto@kernel.org>
---
drivers/idle/intel_idle.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
index 32b3e6049994..338df09ad60b 100644
--- a/drivers/idle/intel_idle.c
+++ b/drivers/idle/intel_idle.c
@@ -1079,8 +1079,6 @@ static int __init intel_idle_cpuidle_driver_init(void)
wrmsrl(MSR_MC6_DEMOTION_POLICY_CONFIG, 0);
}
- on_each_cpu(fix_this_cpu, NULL, 1);
-
return 0;
}
--
2.5.0
next prev parent reply other threads:[~2016-03-14 4:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 1:39 C1E auto-promotion suspend/resume Andy Lutomirski
2016-03-14 4:31 ` Brown, Len
2016-03-14 4:48 ` [PATCH 0/4] intel_idle: Improve MSR fixup resume handling Andy Lutomirski
2016-03-14 4:48 ` [PATCH 1/4] intel_idle: Consolidate auto-promotion/auto-demotion fixups Andy Lutomirski
2016-03-14 4:48 ` Andy Lutomirski [this message]
2016-03-14 4:48 ` [PATCH 3/4] intel_idle: Fix MSRs after resume Andy Lutomirski
2016-03-17 19:41 ` Andy Lutomirski
2016-03-14 4:48 ` [PATCH 4/4] intel_idle: Move BYT/CHT auto-demotion fixup into fix_this_cpu Andy Lutomirski
2016-03-14 5:24 ` C1E auto-promotion suspend/resume Andy Lutomirski
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=7eb5c15595171811aa948480ee51b29fa15fd9b8.1457930807.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=len.brown@intel.com \
--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
all inboxes | Powered by JetHome®