From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:44098) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rl6A6-00075u-6c for qemu-devel@nongnu.org; Wed, 11 Jan 2012 16:56:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rl6A4-0007Vn-I2 for qemu-devel@nongnu.org; Wed, 11 Jan 2012 16:56:50 -0500 Message-ID: <4F0E0537.7090302@suse.de> Date: Wed, 11 Jan 2012 22:55:03 +0100 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <1325783595-22962-1-git-send-email-afaerber@suse.de> <4F0E026B.6010400@suse.de> <4F0E034A.7000109@codemonkey.ws> <3915D4C4-1C96-49AB-82A3-90A916D9D404@suse.de> <9C349219-8BA8-45F6-9B89-99119EFAC837@suse.de> In-Reply-To: <9C349219-8BA8-45F6-9B89-99119EFAC837@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] prep: Fix offset of BIOS MemoryRegion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-ppc@nongnu.org, Avi Kivity , qemu-devel Developers Am 11.01.2012 22:51, schrieb Alexander Graf: >=20 > On 11.01.2012, at 22:49, Alexander Graf wrote: >=20 >> >> On 11.01.2012, at 22:46, Anthony Liguori wrote: >> >>> On 01/11/2012 03:43 PM, Andreas F=E4rber wrote: >>>> Am 05.01.2012 18:13, schrieb Andreas F=E4rber: >>>>> Since 0c90c52fab5ea92d7f12b29bfe26a7cd75d9efcb (ppc_prep: convert t= o memory >>>>> API) OHW was "Trying to execute code outside RAM or ROM at 0xfff007= 00". >>>>> >>>>> The BIOS MemoryRegion is created with a fixed size of 1 MiB. >>>>> Ensure that the full size can be accessed since the exception >>>>> vectors are located at 0xfff00000 and the BIOS may want to use them= . >>>>> >>>>> It thereby no longer depends on the actual BIOS binary size. >>>>> >>>>> Signed-off-by: Andreas F=E4rber >>>>> Cc: Avi Kivity >>>>> Cc: Alexander Graf >>>> >>>> Ping! Is everyone okay with this? Should I send a PULL? >>> >>> I would expect this to come through Alex's tree. >> >> I don't want to have yet another maintainer behind me. PREP and normal= PPC stuff have very little common code, so I would rather have Andreas s= end PULL requests directly. >=20 > Plus I know close to nothing about how PREP works ;). Code that does to= uch common stuff should still either go through my tree or get acked by m= e of course. Please ack my MAINTAINERS update for prep_pci then. I would propose to do the equivalent with grackle and uni-north as part of my upcoming QOM updates, since today there's no obvious connection as far as get_maintainers.pl is concerned. Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg