From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: Cross vendor migration ideas Date: Sat, 15 Nov 2008 14:03:46 +0100 Message-ID: <878wrl16q5.fsf@basil.nowhere.org> References: <982D8D05B6407A49AD506E6C3AC8E7D6BEF936912A@caralain.haven.nynaeve.net> <7CCF7468C07AFF4B991DD1528058EC2F042C7283@SSVLEXMB1.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Skywing" , "Alexander Graf" , "Anthony Liguori" , , "Amit Shah" , "Avi Kivity" , "Wahlig, Elsie" , "Nakajima, Jun" To: "Serebrin, Benjamin (Calendar)" Return-path: Received: from one.firstfloor.org ([213.235.205.2]:51499 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754872AbYKONDq (ORCPT ); Sat, 15 Nov 2008 08:03:46 -0500 In-Reply-To: <7CCF7468C07AFF4B991DD1528058EC2F042C7283@SSVLEXMB1.amd.com> (Benjamin Serebrin's message of "Wed, 12 Nov 2008 17:48:21 -0800") Sender: kvm-owner@vger.kernel.org List-ID: "Serebrin, Benjamin (Calendar)" writes: > > 64-bit OSes will use SYSCALL for 64-bit code. CPUID name string should > be "FakeCPUFakeCPU" One problem is that you'll disable a lot of vendor specific setup code if you do that. Might have all kinds of unexpected side effects. Also it might break user space, unless you key the fake vendor CPUID intercept on ring 0 vs ring 3 (but even if that might not be enough because some kernel modules can call CPUID on their own) I think just emulating SYSCALL/SYSENTER would be safer. It shouldn't be that much slower than int 0x80 hopefully. -Andi