linux-kernel - Re: [PATCH] X86: don't print a warning when MTRR are blank and running in KVM

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: <47BE9E41.9000100@zytor.com>
Date:	Fri, 22 Feb 2008 02:04:49 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Joerg Roedel <joerg.roedel@....com>, tglx@...utronix.de,
	mingo@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] X86: don't print a warning when MTRR are blank and	running
 in KVM

Ingo Molnar wrote:
> * H. Peter Anvin <hpa@...or.com> wrote:
> 
>> Ingo Molnar wrote:
>>> * H. Peter Anvin <hpa@...or.com> wrote:
>>>
>>>>> I'm not sure how we could detect pure Qemu instances - perhaps it should 
>>>>> define some special MSR or something?
>>>> Perhaps they should fix the Qemu BIOS to actually simulate working MSRs; 
>>>> if nothing else, they should set up the default MTRR to be cachable.
>>> btw., should KVM do the same?
>> Yes.  Especially since they share a BIOS.
> 
> ok. Then i guess we should just leave the warning and the backtrace in 
> place until they get a fix done?
> 

That would be my opinion.

Last I checked, they didn't even clear the cache disable bits in %cr0.

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