linux-kernel - Re: Shut up unhandled MSR warnings

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <56446AFD.4030800@redhat.com>
Date:	Thu, 12 Nov 2015 11:33:33 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Jörg Rödel <joro@...tes.org>,
	kvm ML <kvm@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Shut up unhandled MSR warnings



On 12/11/2015 11:13, Borislav Petkov wrote:
> Hey Paolo,
> 
> do we apply stuff like that below?

If we really need to, we do.

> When booting guests all the time here, dmesg gets filled up with those
> "unhandled rdmsr" useless warnings. The patch below shuts them up.
> 
> The only problem is that the IC CFG MSR has those fields
> defined starting from F15h and I don't see a way to check the
> family/model/stepping of the guest CPU in kvm. Is there?

Yes, see guest_cpuid_has_* for an example of reading the CPUID values.

But if it's defined for _all_ models starting at family 21, we can just
do it unconditionally.

Paolo
--
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/