qemu-arm
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-arm] [Qemu devel v9 PATCH 2/5] msf2: Microsemi Smartfusion2 Sy


From: Peter Maydell
Subject: Re: [Qemu-arm] [Qemu devel v9 PATCH 2/5] msf2: Microsemi Smartfusion2 System Register block
Date: Mon, 18 Sep 2017 15:39:00 +0100

On 18 September 2017 at 15:22, Philippe Mathieu-Daudé <address@hidden> wrote:
> On 09/18/2017 11:00 AM, Peter Maydell wrote:
>> There's lots of stuff that can cause the guest to go badly
>> and confusingly wrong if unimplemented. If we print a
>> useful message with LOG_UNIMP then there's an easy clue
>> for what's gone wrong. The guest shouldn't be able to
>> provoke QEMU to exit.
>
>
> I understand. I'm worried about being PITA for an user to figure out what's
> happening here, that's why I'm wondering how this should be handled. Another
> idea I thought about was raising a PREFETCH or BKPT exception, but this
> would also be an incorrect model behavior.
>
> Anyway I'd be happy enough if instead of using LOG_UNIMP/LOG_GUEST_ERROR we
> use an unconditional qemu_log("bus remap unimplemented, unpredictable
> behaviour!") warning. Fair enough?

I don't see any reason to handle this any differently to
anything else.

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]