From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
Zha Bin <zhabin@linux.alibaba.com>,
Jing Liu <jing2.liu@linux.intel.com>,
Chao Peng <chao.p.peng@linux.intel.com>
Subject: Re: [virtio-dev] On doorbells (queue notifications)
Date: Wed, 15 Jul 2020 14:29:04 +0100 [thread overview]
Message-ID: <877dv4ykin.fsf@linaro.org> (raw)
In-Reply-To: <20200715114855.GF18817@stefanha-x1.localdomain>
Stefan Hajnoczi <stefanha@redhat.com> writes:
> On Tue, Jul 14, 2020 at 10:43:36PM +0100, Alex Bennée wrote:
>> I'm slightly confused by the MSI terminology because this only seems to
>> be relevant for the PCI legacy interface and AFAICT only touch the
>> outgoing path in setup and del_vq. Do incoming MSI interrupts just get
>> mapped directly to the appropriate handler function to process the
>> queues or the config?
>
> When MSI is used the VIRTIO ISR register does not need to be read by the
> guest interrupt handler.
>
>> Finally I'm curious if this is just a problem avoided by the s390
>> channel approach? Does the use of messages over a channel just avoid the
>> sort of bouncing back and forth that other hypervisors have to do when
>> emulating a device?
>
> What does "bouncing back and forth" mean exactly?
Context switching between guest and hypervisor.
>
> Stefan
--
Alex Bennée
---------------------------------------------------------------------
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:[~2020-07-15 13:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 21:43 [virtio-dev] On doorbells (queue notifications) Alex Bennée
2020-07-15 11:48 ` Stefan Hajnoczi
2020-07-15 13:29 ` Alex Bennée [this message]
2020-07-15 15:47 ` Stefan Hajnoczi
2020-07-15 16:40 ` Alex Bennée
2020-07-15 17:09 ` Cornelia Huck
2020-07-16 10:00 ` Stefan Hajnoczi
2020-07-16 11:25 ` Christophe de Dinechin
2020-07-16 14:19 ` Stefan Hajnoczi
2020-07-16 14:31 ` Christophe de Dinechin
2020-07-16 14:34 ` Christophe de Dinechin
2020-07-17 8:42 ` Stefan Hajnoczi
2020-07-15 17:01 ` Cornelia Huck
2020-07-15 17:25 ` Alex Bennée
2020-07-15 20:04 ` Halil Pasic
2020-07-16 9:41 ` Cornelia Huck
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=877dv4ykin.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=chao.p.peng@linux.intel.com \
--cc=jing2.liu@linux.intel.com \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=zhabin@linux.alibaba.com \
/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