From: Dave Jones <davej@redhat.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: Re: [PATCH] cpufreq/intel_pstate: Add function to check that all MSR's are valid
Date: Fri, 22 Mar 2013 11:06:47 -0400 [thread overview]
Message-ID: <20130322150647.GA1632@redhat.com> (raw)
In-Reply-To: <1589305.6YMuneKuPN@vostro.rjw.lan>
On Fri, Mar 22, 2013 at 01:40:49AM +0100, Rafael J. Wysocki wrote:
> On Thursday, March 21, 2013 01:08:03 AM Rafael J. Wysocki wrote:
> > On Wednesday, March 20, 2013 11:28:49 AM Dirk Brandewie wrote:
> > > On 03/20/2013 11:28 AM, Rafael J. Wysocki wrote:
> > > > On Wednesday, March 20, 2013 09:17:24 AM dirk.brandewie@gmail.com wrote:
> > > >> From: Dirk Brandewie <dirk.brandewie@gmail.com>
> > > >>
> > > >> Some VMs seem to try to implement some MSRs but not all the registers
> > > >> the driver needs. Check to make sure all the MSR that we need are
> > > >> available. If any of the required MSRs are not available refuse to
> > > >> load.
> > > >>
> > > >> Signed-off-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
> > > >
> > > > Is this needed for v3.9? Any pointers to bug reports etc.?
> > > >
> > >
> > > Sorry I saw right after I sent the mail that the bug report was missing
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=922923
> > > Reported-by: Josh Stone <jistone@redhat.com>
> > >
> > > Would you like me to spin the patch?
> >
> > No, thanks, this information is sufficient.
>
> Applied to linux-pm.git/bleeding-edge and will be moved to linux-next after
> build testing.
'next' seems to be imply you're targetting this for 3.10 ?
In case it wasn't clear, this is needed for 3.9.
Dave
next prev parent reply other threads:[~2013-03-22 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 16:17 [PATCH] cpufreq/intel_pstate: Add function to check that all MSR's are valid dirk.brandewie
2013-03-20 18:28 ` Rafael J. Wysocki
2013-03-20 18:28 ` Dirk Brandewie
2013-03-21 0:08 ` Rafael J. Wysocki
2013-03-22 0:40 ` Rafael J. Wysocki
2013-03-22 15:06 ` Dave Jones [this message]
2013-03-23 0:06 ` Rafael J. Wysocki
2013-03-21 3:20 ` Viresh Kumar
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=20130322150647.GA1632@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@vger.kernel.org \
--cc=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).