From: Johannes Berg <johannes@sipsolutions.net>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC v2 1/2] docs: vhost-user: add in-band kick/call messages
Date: Thu, 12 Sep 2019 10:13:28 +0200 [thread overview]
Message-ID: <cd8efde95c4edf806af3c2255e52be0567302f7e.camel@sipsolutions.net> (raw)
In-Reply-To: <20190912080932.GA2722@work-vm>
On Thu, 2019-09-12 at 09:09 +0100, Dr. David Alan Gilbert wrote:
>
> You're actually using the same trick of using
> REPLY_ACK/need_reply to make it synchronous that set_mem_table does;
I don't think it's really the same - though arguably I could have
spec'ed the inband signal to *require* an ACK. The way I did it relies
on the REPLY_ACK extension.
SET_MEM_TABLE actually specifies a 3-way handshake, qemu->device,
device->qemu, qemu->device.
> that makes sense - but then new calls are getting it to actually process
> some data/commands on the ring itself?
No, the calls (or more specifically the REPLY_ACK to them) are really in
simulation to only acknowledge the interrupt (kick/call) signal has been
received and accounted for on the simulation calendar, the actual
processing happens when the calendar event is scheduled.
johannes
next prev parent reply other threads:[~2019-09-12 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 13:45 [Qemu-devel] [RFC v2 0/2] vhost-user: in-band notifications Johannes Berg
2019-09-11 13:45 ` [Qemu-devel] [RFC v2 1/2] docs: vhost-user: add in-band kick/call messages Johannes Berg
2019-09-11 14:07 ` Michael S. Tsirkin
2019-09-11 15:09 ` Johannes Berg
2019-09-16 11:40 ` Johannes Berg
2019-09-16 15:30 ` Michael S. Tsirkin
2019-09-17 12:01 ` Johannes Berg
2019-09-11 19:15 ` Dr. David Alan Gilbert
2019-09-11 19:18 ` Johannes Berg
2019-09-12 8:09 ` Dr. David Alan Gilbert
2019-09-12 8:13 ` Johannes Berg [this message]
2019-09-11 13:45 ` [Qemu-devel] [RFC v2 2/2] libvhost-user: implement in-band notifications Johannes Berg
2019-09-11 15:01 ` [Qemu-devel] [RFC v2 0/2] vhost-user: " no-reply
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=cd8efde95c4edf806af3c2255e52be0567302f7e.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dgilbert@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).