From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: 1806824@bugs.launchpad.net, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1806824] Re: SIE-200 (TrustZone) MPC: BLK_MAX returns an incorrect value
Date: Fri, 14 Dec 2018 14:58:43 +0000 [thread overview]
Message-ID: <87h8fg17fg.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA9ZjB8FidPOyjKwqP+PMaoNfD0szVk_XbQk11LzSU_ZfQ@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On Fri, 14 Dec 2018 at 13:56, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>>
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>
>> > Thanks for the bug report and the test program. The fix seems straightforward -- just adjust what we return for the register value. I've sent a patch:
>> > http://patchwork.ozlabs.org/patch/1013034/
>>
>> I know you had a bunch of M-profile test cases. Once we get tcg system
>> tests enabled would it be worth porting some of those into the QEMU src
>> tree?
>
> I don't have anything suitable -- unless we have
> support for "system test of this guest kernel", in which case
> we could add the arm trusted firmware boot/selftests.
That's the next step, enabling the building of a known good test case
from an external tree and depositing the images in the right place so we
can use them as tests.
Things like LTP, kvm-unit-tests and various kernels.
>
> thanks
> -- PMM
--
Alex Bennée
next prev parent reply other threads:[~2018-12-14 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 6:43 [Qemu-devel] [Bug 1806824] [NEW] SIE-200 (TrustZone) MPC: BLK_MAX returns an incorrect value YVT
2018-12-05 11:05 ` [Qemu-devel] [Bug 1806824] " Alex Bennée
2018-12-13 16:08 ` YVT
2018-12-13 18:35 ` Peter Maydell
2018-12-14 13:53 ` Alex Bennée
2018-12-14 14:23 ` Peter Maydell
2018-12-14 14:58 ` Alex Bennée [this message]
2019-04-24 5:33 ` Thomas Huth
2019-04-24 5:33 ` Thomas Huth
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=87h8fg17fg.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=1806824@bugs.launchpad.net \
--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).