[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ec003137-c08f-cda6-6a94-d37d5460189c@linux.intel.com>
Date: Mon, 6 Jan 2020 15:24:18 +0800
From: "Liu, Jing2" <jing2.liu@...ux.intel.com>
To: "Michael S. Tsirkin" <mst@...hat.com>,
"Liu, Jiang" <gerry@...ux.alibaba.com>
Cc: Jason Wang <jasowang@...hat.com>,
Zha Bin <zhabin@...ux.alibaba.com>,
linux-kernel@...r.kernel.org, slp@...hat.com,
virtio-dev@...ts.oasis-open.org, jing2.liu@...el.com,
chao.p.peng@...el.com
Subject: Re: [PATCH v1 2/2] virtio-mmio: add features for virtio-mmio
specification version 3
On 1/5/2020 6:42 PM, Michael S. Tsirkin wrote:
> On Thu, Dec 26, 2019 at 09:16:19PM +0800, Liu, Jiang wrote:
>>> 2) The mask and unmask control is missed
>>>
>>>
>>>> but the extension doesn’t support 3) because
>>>> we noticed that the Linux virtio subsystem doesn’t really make use of interrupt masking/unmasking.
> Linux uses masking/unmasking in order to migrate interrupts between
> CPUs.
Hi Michael,
Thanks for reviewing the patches!
When trying to study the mask/unmask use case during migrating irq, it
seems being used e.g.
1) migrate irq(s) away from offline cpu
2) irq affinity is changing, while an interrupt comes so it sets
SETAFFINITY_PENDING and
the lapic (e.g. x86) does the mask and unmask to finish the pending
during ack.
Is this right? So we should have mask/unmask for each vector.
Thanks,
Jing
Powered by blists - more mailing lists