lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 23 Mar 2013 01:06:47 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Dave Jones <davej@...hat.com>
Cc:	Dirk Brandewie <dirk.brandewie@...il.com>,
	linux-kernel@...r.kernel.org, cpufreq@...r.kernel.org,
	Dirk Brandewie <dirk.j.brandewie@...el.com>
Subject: Re: [PATCH] cpufreq/intel_pstate: Add function to check that all MSR's are valid

On Friday, March 22, 2013 11:06:47 AM Dave Jones wrote:
> 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@...il.com wrote:
>  > > > >> From: Dirk Brandewie <dirk.brandewie@...il.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@...el.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@...hat.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.

I'm going to push this for 3.9 after it has spent a couple of days in
linux-next just in case.  So 3.9-rc5 is the target.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ