From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753566AbYIZRi5 (ORCPT ); Fri, 26 Sep 2008 13:38:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752209AbYIZRiu (ORCPT ); Fri, 26 Sep 2008 13:38:50 -0400 Received: from terminus.zytor.com ([198.137.202.10]:37182 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751395AbYIZRit (ORCPT ); Fri, 26 Sep 2008 13:38:49 -0400 Message-ID: <48DD1DE1.5070708@zytor.com> Date: Fri, 26 Sep 2008 10:37:37 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Valdis.Kletnieks@vt.edu CC: Gerd Hoffmann , Zachary Amsden , Alok Kataria , Alok kataria , Ingo Molnar , Yan Li , "linux-kernel@vger.kernel.org" , "joerg.roedel@amd.com" , "rjmaomao@gmail.com" , Yinghai Lu , Thomas Gleixner , Daniel Hecht Subject: Re: [PATCH 1/2] VMware detection support for x86 and x86-64 References: <20080221115452.GB13948@elte.hu> <20080907234510.GA24133@yantp.cn.ibm.com> <20080908140423.GG11993@elte.hu> <35f686220809241928k3669e30bi8a98b440443c4bff@mail.gmail.com> <48DB15DB.8040501@zytor.com> <1222317978.23524.117.camel@alok-dev1> <48DB1984.8020704@zytor.com> <1222318928.23524.121.camel@alok-dev1> <48DB1BCE.2070106@zytor.com> <1222320201.23524.135.camel@alok-dev1> <1222375694.27056.179.camel@bodhitayantram.eng.vmware.com> <48DC09D9.7040204@zytor.com> <1222381254.27056.194.camel@bodhitayantram.eng.vmware.com> <48DC105D.9050803@zytor.com> <48DCD9D9.9080008@redhat.com> <40178.1222435332@turing-police.cc.vt.edu> In-Reply-To: <40178.1222435332@turing-police.cc.vt.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Valdis.Kletnieks@vt.edu wrote: > Which would be hardware implementers in the '80s getting wrong the first few > times what IBM did right the first time. Doesn't *anybody* do literature > searches before doing stuff anymore? ;) Well, yes. There are some prety strong reasons to believe that Intel got that one wrong *deliberately*, until VMware finally forced their hand. -hpa