From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Yang, Sheng" Subject: Re: [PATCH] kvm: bios: Put AP boot up code to 0x1000 Date: Thu, 31 Jul 2008 17:09:29 +0800 Message-ID: <200807311709.29198.sheng.yang@intel.com> References: <200807311043.20880.sheng.yang@intel.com> <200807311400.11644.sheng.yang@intel.com> <48915E80.8010406@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mga11.intel.com ([192.55.52.93]:18320 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752355AbYGaJHT (ORCPT ); Thu, 31 Jul 2008 05:07:19 -0400 In-Reply-To: <48915E80.8010406@qumranet.com> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: On Thursday 31 July 2008 14:41:04 Avi Kivity wrote: > Yang, Sheng wrote: > > On Thursday 31 July 2008 10:43:20 Yang, Sheng wrote: > >> From ba05b3c821400127074f65ee4d172fabbe3524cd Mon Sep 17 > >> 00:00:00 2001 From: Sheng Yang > >> Date: Thu, 31 Jul 2008 10:39:24 +0800 > >> Subject: [PATCH] kvm: bios: Put AP boot up code to 0x1000 > >> > >> Rather than 0x10000, which can be overrided by userspace program > >> like grub. > > How about 0xex000? And avoid copying the bios to low memory? > > Gleb tried it and it worked. We'd have to change qemu to mark the > memory as RAM, not ROM, but that's what real hardware does as well > (shadowing the ROM into RAM). I tried 0xea000, and it's fine. But avoid copying is better. But I don't understand the RAM/ROM issue in qemu here... And do you mean you have patch on hand now? :) -- regards Yang, Sheng