[Top][All Lists]

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

Re: [Qemu-devel] [PATCH 23/27] hw/core/or-irq: Support more than 16 inpu

From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH 23/27] hw/core/or-irq: Support more than 16 inputs to an OR gate
Date: Thu, 31 May 2018 12:21:19 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

On 30/05/2018 19:35, Peter Maydell wrote:
> On 30 May 2018 at 17:59, Paolo Bonzini <address@hidden> wrote:
>> On 21/05/2018 17:02, Peter Maydell wrote:
>>> On 21 May 2018 at 15:34, Paolo Bonzini <address@hidden> wrote:
>>>> Why do the levels have to be migrated at all?  It should be enough if
>>>> the IRQ level is either migrated manually, or restored (e.g. in
>>>> post_save callbacks) through other data that is migrated.
>>> This is standard behaviour for devices: they track their
>>> inbound irq/gpio lines, and then that becomes internal state for
>>> them that must be migrated.
>> But or_irq's input are another device's outbound lines, so tracking them
>> should not be necessary.  The other device would do it for or_irq.
> There's no mechanism in qemu_irq for the destination end to ask
> the source end about its current value. The information flow
> is strictly one-way.

On postload, the source must call qemu_set_irq and that will cause an
update of the or_irq, won't it?


reply via email to

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