From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-ppc@nongnu.org, Avi Kivity <avi@redhat.com>,
qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] prep: Fix offset of BIOS MemoryRegion
Date: Wed, 11 Jan 2012 22:55:03 +0100 [thread overview]
Message-ID: <4F0E0537.7090302@suse.de> (raw)
In-Reply-To: <9C349219-8BA8-45F6-9B89-99119EFAC837@suse.de>
Am 11.01.2012 22:51, schrieb Alexander Graf:
>
> On 11.01.2012, at 22:49, Alexander Graf wrote:
>
>>
>> On 11.01.2012, at 22:46, Anthony Liguori wrote:
>>
>>> On 01/11/2012 03:43 PM, Andreas Färber wrote:
>>>> Am 05.01.2012 18:13, schrieb Andreas Färber:
>>>>> Since 0c90c52fab5ea92d7f12b29bfe26a7cd75d9efcb (ppc_prep: convert to memory
>>>>> API) OHW was "Trying to execute code outside RAM or ROM at 0xfff00700".
>>>>>
>>>>> 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ärber<afaerber@suse.de>
>>>>> Cc: Avi Kivity<avi@redhat.com>
>>>>> Cc: Alexander Graf<agraf@suse.de>
>>>>
>>>> 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 send PULL requests directly.
>
> Plus I know close to nothing about how PREP works ;). Code that does touch common stuff should still either go through my tree or get acked by me 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
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-01-11 21:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 17:13 [Qemu-devel] [PATCH] prep: Fix offset of BIOS MemoryRegion Andreas Färber
2012-01-11 21:43 ` Andreas Färber
2012-01-11 21:46 ` Anthony Liguori
2012-01-11 21:49 ` Alexander Graf
2012-01-11 21:51 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2012-01-11 21:55 ` Andreas Färber [this message]
2012-01-11 21:58 ` Alexander Graf
2012-01-11 22:04 ` [Qemu-devel] " Anthony Liguori
2012-01-11 23:12 ` [Qemu-devel] [PATCH] PREP: Finish qdev conversion Alexander Graf
2012-01-16 14:36 ` [Qemu-devel] [PATCH] prep: Fix offset of BIOS MemoryRegion Andreas Färber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0E0537.7090302@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).