From: "Michael S. Tsirkin" <mst@redhat.com>
To: Usama Arif <usama.arif@bytedance.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
virtio-dev@lists.oasis-open.org, ndragazis@arrikto.com,
fam.zheng@bytedance.com, liangma@liangbit.com
Subject: [virtio-dev] Re: [External] Re: [PATCH v3 3/4] content: Introduce driver/device auxiliary notifications for MMIO
Date: Mon, 31 Oct 2022 11:47:55 -0400 [thread overview]
Message-ID: <20221031114727-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <a0773598-1ce5-1b98-5aa1-95350bccdbb6@bytedance.com>
On Mon, Oct 31, 2022 at 02:22:22PM +0000, Usama Arif wrote:
>
>
> On 27/10/2022 22:27, Stefan Hajnoczi wrote:
> > On Fri, Oct 07, 2022 at 05:56:42PM +0100, Usama Arif wrote:
> > > This includes the additions to the corresponding device and driver
> > > conformances.
> > >
> > > Signed-off-by: Usama Arif <usama.arif@bytedance.com>
> > > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> >
> > You can keep this. One thought:
> >
> > I realized that virtio-mmio support won't be very useful until
> > virtio-mmio gets MSI-X support because drivers currently cannot
> > differentiate between device auxiliary notifications.
> >
> > Stefan
>
> Did you mean drivers currently cannot differentiate between "driver"
> auxiliary notifications? The driver will be able to be able to choose the
> index it wants to notifiy using DeviceAuxNotificationIndex.
>
> I can add the following line in the Interrupt Status change of the patch if
> it makes sense?
> "As MSI-X is not available, it is not possible to determine which driver
drop "As MSI-X is not available," msi-x is a pci technology.
> auxiliary notification occured, hence only a single notification is
> supported."
>
> Thanks,
> Usama
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2022-10-31 15:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 16:56 [virtio-dev] [PATCH v3 0/4] Introduce aux. notifications and virtio-vhost-user Usama Arif
2022-10-07 16:56 ` [virtio-dev] [PATCH v3 1/4] content: Introduce driver/device auxiliary notifications Usama Arif
2022-10-11 9:20 ` Cornelia Huck
2022-10-11 16:58 ` Usama Arif
2022-10-27 20:05 ` [virtio-dev] " Stefan Hajnoczi
2022-10-28 10:05 ` [virtio-dev] Re: [External] " Usama Arif
2022-10-07 16:56 ` [virtio-dev] [PATCH v3 2/4] content: Introduce driver/device aux. notification cfg type for PCI Usama Arif
2022-10-27 21:22 ` [virtio-dev] " Stefan Hajnoczi
2022-10-07 16:56 ` [virtio-dev] [PATCH v3 3/4] content: Introduce driver/device auxiliary notifications for MMIO Usama Arif
2022-10-27 21:27 ` [virtio-dev] " Stefan Hajnoczi
2022-10-31 14:22 ` [virtio-dev] Re: [External] " Usama Arif
2022-10-31 15:47 ` Michael S. Tsirkin [this message]
2022-10-31 17:26 ` Stefan Hajnoczi
2022-10-31 15:45 ` [virtio-dev] " Michael S. Tsirkin
2022-10-31 17:24 ` Stefan Hajnoczi
2022-10-31 19:33 ` Michael S. Tsirkin
2022-10-07 16:56 ` [virtio-dev] [PATCH v3 4/4] vhost-user: add vhost-user device type Usama Arif
2022-10-27 19:54 ` [virtio-dev] Re: [PATCH v3 0/4] Introduce aux. notifications and virtio-vhost-user Stefan Hajnoczi
2022-10-28 16:36 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221031114727-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=fam.zheng@bytedance.com \
--cc=liangma@liangbit.com \
--cc=ndragazis@arrikto.com \
--cc=stefanha@redhat.com \
--cc=usama.arif@bytedance.com \
--cc=virtio-dev@lists.oasis-open.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox