qemu-devel
[Top][All Lists]
Advanced

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

Re: [PATCH] risu: don't do a full register compare for OP_SIGILL


From: Richard Henderson
Subject: Re: [PATCH] risu: don't do a full register compare for OP_SIGILL
Date: Tue, 23 Jun 2020 12:55:09 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0

On 6/23/20 9:17 AM, Alex Bennée wrote:
> 
> Peter Maydell <peter.maydell@linaro.org> writes:
> 
>> On Tue, 23 Jun 2020 at 16:07, Alex Bennée <alex.bennee@linaro.org> wrote:
>>>
>>> OP_SIGILL means we have an unexpected invalid operation. If this is a
>>> load or store the register state may be un-rectified pointing at the
>>> memblock so would be invalid. In this case just compare the PC and
>>> make sure the other end also faulted at the same place.
>>
>> In case of mismatch of the PC do we still print the full register
>> dump?

No.  If we want that, we should do something else, like remember that the
memory pointer is in use and zap it out before reporting the register set.

But, generally, if we see SIGILL, then we have not actually executed anything,
so the register state doesn't matter too much.  What probably does want
reporting in this case is the insn opcode.


r~



reply via email to

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