qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] virtio device error reporting best practice?


From: Venkatesh Srinivas
Subject: Re: [Qemu-devel] virtio device error reporting best practice?
Date: Wed, 26 Mar 2014 17:54:26 -0700

On Wed, Mar 26, 2014 at 7:34 AM, Markus Armbruster <address@hidden> wrote:
> Peter Maydell <address@hidden> writes:
>
>> On 20 March 2014 06:39, Markus Armbruster <address@hidden> wrote:
>>> Time to cease the practice.  Will be hard as long as the code
>>> is chock-full of bad examples.
>>
>> I've been consistently rejecting new instances of
>> guest triggerable exit() or abort() in code review when
>> I see them for at least the last six months to a year or so
>> (since we improved the qemu_log() facility so it could be
>> used by device models too).
>
> Appreciated.

How are these errors expected to be reflected into guests? PCI aborts
could be one place to stand, for example.

-- vs;



reply via email to

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