Re: Shut up unhandled MSR warnings

2015-11-12 Thread Paolo Bonzini
On 12/11/2015 13:16, Borislav Petkov wrote: >>> > > 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. >> > >> > The thing is, those bits are Reserved again

Re: Shut up unhandled MSR warnings

2015-11-12 Thread Borislav Petkov
On Thu, Nov 12, 2015 at 11:59:58AM +0100, Borislav Petkov wrote: > On Thu, Nov 12, 2015 at 11:33:33AM +0100, Paolo Bonzini wrote: > > 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 unc

Re: Shut up unhandled MSR warnings

2015-11-12 Thread Borislav Petkov
On Thu, Nov 12, 2015 at 11:33:33AM +0100, Paolo Bonzini wrote: > 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. The thing is, those bits are Reserved again on the next fami

Re: Shut up unhandled MSR warnings

2015-11-12 Thread Paolo Bonzini
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 th

Shut up unhandled MSR warnings

2015-11-12 Thread Borislav Petkov
Hey Paolo, do we apply stuff like that below? 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 che