From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752596AbYI3Dwn (ORCPT ); Mon, 29 Sep 2008 23:52:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751157AbYI3Dwf (ORCPT ); Mon, 29 Sep 2008 23:52:35 -0400 Received: from terminus.zytor.com ([198.137.202.10]:44578 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751087AbYI3Dwe (ORCPT ); Mon, 29 Sep 2008 23:52:34 -0400 Message-ID: <48E1A199.8010906@zytor.com> Date: Mon, 29 Sep 2008 20:48:41 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: "Nakajima, Jun" CC: "akataria@vmware.com" , Jeremy Fitzhardinge , Gerd Hoffmann , Ingo Molnar , Thomas Gleixner , LKML , the arch/x86 maintainers , "avi@redhat.com" , Rusty Russell , Zach Amsden , Daniel Hecht Subject: Re: Use CPUID to communicate with the hypervisor. References: <1222472815.29886.43.camel@alok-dev1> <48E090B6.2080809@redhat.com> <1222710924.30247.21.camel@alok-dev1> <48E1227B.9040809@redhat.com> <1222717085.30247.44.camel@alok-dev1> <0B53E02A2965CE4F9ADB38B34501A3A15726E15A@orsmsx505.amr.corp.intel.com> <48E1437D.7080606@zytor.com> <48E1486C.3060306@goop.org> <1222733523.30247.91.camel@alok-dev1> <48E17363.7060103@zytor.com> <0B53E02A2965CE4F9ADB38B34501A3A15726E51D@orsmsx505.amr.corp.intel.com> <48E17999.8080403@zytor.com> <0B53E02A2965CE4F9ADB38B34501A3A15726E52E@orsmsx505.amr.corp.intel.com> <48E18D21.8040305@zytor.com> <0B53E02A2965CE4F9ADB38B34501A3A15726E5B1@orsmsx505.amr.corp.intel.com> In-Reply-To: <0B53E02A2965CE4F9ADB38B34501A3A15726E5B1@orsmsx505.amr.corp.intel.com> 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 Nakajima, Jun wrote: >>> >> OK, if so we should write up a formal proposal. > > I assume that the scope is limited to virtualization of Linux. > That's part of the problem -- it's not, and it can't be. It's about the hypervisor providing a specific service to its guest, and although we can explain how Linux would use this, there is going to be an expectation -- especially for Microsoft and Apple -- that other OSes would use the same interfaces (to the extent they care, obviously.) -hpa