From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Jan Kiszka <jan.kiszka@web.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] Revert "memory: Return -1 again on reads from unsigned regions"
Date: Thu, 08 Aug 2013 18:55:02 +0200 [thread overview]
Message-ID: <5203CD66.1050200@suse.de> (raw)
In-Reply-To: <CAFEAcA9TQWeWy0JKrbhAT8XU8WLm+cpuyV65hrfGTwh=Uaq4Lg@mail.gmail.com>
Am 08.08.2013 18:48, schrieb Peter Maydell:
> On 8 August 2013 17:46, Andreas Färber <afaerber@suse.de> wrote:
>> Since no one has spoken up with a concrete use case that breaks when
>> having the PIO region opaque, I agree this seems the best solution we
>> have for 1.6. But given the musicpal issue you have raised, I would ask
>> Paolo or Jan to squash these two patches together to avoid a git-bisect
>> regression.
>
> Not sure what you have in mind here -- musicpal is an ARM
> board, and no ARM system should ever touch the system_io
> region at all, so for musicpal patch 1/2 has no effect
> and we care only about 2/2.
Sorry, mixed up your other reply with this non-threaded series - thought
you were saying 1/2 introduced the regression, but the regression is
already in qemu.git I understand just like for prep.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-08-08 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51FCBF4E.90605@web.de>
2013-08-03 8:31 ` [Qemu-devel] [PATCH 2/2] Revert "memory: Return -1 again on reads from unsigned regions" Jan Kiszka
2013-08-08 15:23 ` Peter Maydell
2013-08-08 15:27 ` Jan Kiszka
2013-08-08 16:46 ` Andreas Färber
2013-08-08 16:48 ` Peter Maydell
2013-08-08 16:55 ` Andreas Färber [this message]
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=5203CD66.1050200@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@web.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).