All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Usama Arif <usama.arif@bytedance.com>,
	virtio-dev@lists.oasis-open.org, ndragazis@arrikto.com,
	fam.zheng@bytedance.com, liangma@liangbit.com
Subject: Re: [virtio-dev] Re: [PATCH v3 3/4] content: Introduce driver/device auxiliary notifications for MMIO
Date: Mon, 31 Oct 2022 15:33:05 -0400	[thread overview]
Message-ID: <20221031153240-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <Y2AEzkxKVw46JUGE@fedora>

On Mon, Oct 31, 2022 at 01:24:30PM -0400, Stefan Hajnoczi wrote:
> On Mon, Oct 31, 2022 at 11:45:55AM -0400, Michael S. Tsirkin wrote:
> > On Thu, Oct 27, 2022 at 05:27:28PM -0400, 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
> > 
> > 
> > The big issue with MSI is it actually needs a ton of registers
> > for interrupt rebalancing, masking etc and they need to be fast.
> > Maybe a status bit like pci has makes sense here.
> 
> This patch does add an ISR bit:
> 
> diff --git a/content.tex b/content.tex
> index 33362b7..8968fcd 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -2049,6 +2049,8 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi
>          in at least one of the active virtual queues.
>        \item [Configuration Change Notification] - bit 1 - the interrupt was
>          asserted because the configuration of the device has changed.
> +      \item [Device-specific Driver Auxiliary Notification] - bit 2 - the interrupt was
> +        asserted because a device-specific event occurred to notify the driver.
> 
> The problem is that the driver doesn't know which device-specific event
> occurred, so the mechanism is less useful than the MSI-X approach where
> the driver knows exactly which (of potentially many) device-specific
> events occurred.
> 
> Stefan


Right I figured that out after sending this. So it's limited to
one event type.


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2022-10-31 19:33 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
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 [this message]
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=20221031153240-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.