linux-kernel - Re: [PATCH 1/2] VMware guest detection for x86 and x86-64

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]

Date:	Thu, 25 Sep 2008 22:38:25 +0800
From:	Yan Li <elliot.li.tech@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Greg KH <greg@...ah.com>, Yan Li <elliot.li.tech@...il.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	joerg.roedel@....com, rjmaomao@...il.com,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>, nancydreaming@...il.com
Subject: Re: [PATCH 1/2] VMware guest detection for x86 and x86-64

On Wed, Sep 24, 2008 at 09:54:36PM -0700, H. Peter Anvin wrote:
> We pretty much have to, just as we have to work around bugs in, say,  
> AMD's microcode.  We have avoided it so far, but it's gotten to a  
> breaking point, and rather than having ad hoc hacks scattered all over  
> the place I want a centralized test site setting a single global 
> variable.

That sounds great but technically this centralized test can only be
done after dmi_scan_machine(), so it can't help the detection code in
mtrr_trim_uncached_memory() which is ran very early before
dmi_scan_machine(). So I think my patch is still necessary unless we
want to live with the warning message in all VMware guest.

-- 
Li, Yan
--
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/