From: Claudio Fontana <claudio.fontana@huawei.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [ARM][regression][bisect] ARM target broken: test v5 image does not start kernel
Date: Thu, 5 Sep 2013 12:59:58 +0200 [thread overview]
Message-ID: <5228642E.4070606@huawei.com> (raw)
In-Reply-To: <CAFEAcA8cyyfUKNTwZOYWYe5CA5Rn4_tqON_E4O3jcTnqRdYcsQ@mail.gmail.com>
Hi Peter,
On 05.09.2013 10:59, Peter Maydell wrote:
> On 5 September 2013 09:31, Claudio Fontana <claudio.fontana@huawei.com> wrote:
>
>> I just finished bisecting a regression I am experiencing on ARM 32bit target,
>
>> After a painful bisection, I got a first bad commit, which when reverted on the latest QEMU fixes the issue for me. Maybe something needs to be adapted to the return value (back-)change?
>
>> 9b8c69243585a32d14b9bb9fcd52c37b0b5a1b71 is the first bad commit
>> commit 9b8c69243585a32d14b9bb9fcd52c37b0b5a1b71
>> Author: Jan Kiszka <jan.kiszka@siemens.com>
>> Date: Tue Jul 16 14:45:16 2013 +0200
>>
>> memory: Return -1 again on reads from unsigned regions
>
> This one again! Claudio, can you test with these patches:
> http://patchwork.ozlabs.org/patch/272011/
> http://patchwork.ozlabs.org/patch/272012/
>
> which Jan posted earlier this week and should fix
> this regression?
>
> thanks
> -- PMM
Yes, this fixes it. I hope the fix lands in mainline soon.
Thanks,
Claudio
--
Claudio Fontana
Server OS Architect
Huawei Technologies Duesseldorf GmbH
prev parent reply other threads:[~2013-09-05 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 8:31 [Qemu-devel] [ARM][regression][bisect] ARM target broken: test v5 image does not start kernel Claudio Fontana
2013-09-05 8:59 ` Peter Maydell
2013-09-05 10:59 ` Claudio Fontana [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=5228642E.4070606@huawei.com \
--to=claudio.fontana@huawei.com \
--cc=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).