qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org, kraxel@redhat.com
Subject: [Qemu-devel] Re: [PATCHv5 04/11] virtio: notifier support + APIs for queue fields
Date: Wed, 17 Mar 2010 09:44:05 +0530	[thread overview]
Message-ID: <20100317041405.GD20122@amit-x200.redhat.com> (raw)
In-Reply-To: <8cc7396586d6e6caf90611dbddd8eb901b3ecaf4.1268758544.git.mst@redhat.com>

On (Tue) Mar 16 2010 [19:10:58], Michael S. Tsirkin wrote:
> 
> diff --git a/hw/virtio.c b/hw/virtio.c
> index 7c020a3..f54129f 100644
> --- a/hw/virtio.c
> +++ b/hw/virtio.c
> @@ -73,6 +73,9 @@ struct VirtQueue
>      int inuse;
>      uint16_t vector;
>      void (*handle_output)(VirtIODevice *vdev, VirtQueue *vq);
> +    VirtIODevice *vdev;
> +    EventNotifier guest_notifier;
> +    EventNotifier host_notifier;

Another thing that terribly confused me was this: in the vq struct you
have guest_notifier and host_notifier of type EventNotifier and in the
virtio binding structs you have guest_notifier and host_notifier which
are function callbacks.

Also, these vq->{guest_|host_}notifier assignments weren't easily found
using grep because they're assigned by assigning a pointer value and
initialising that pointer. Thanks to Juan for finding that for me :-)

		Amit
-- 
http://log.amitshah.net/

  reply	other threads:[~2010-03-17  4:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 17:10 [Qemu-devel] [PATCHv5 00/11] vhost-net: upstream integration Michael S. Tsirkin
2010-03-16 17:10 ` [Qemu-devel] [PATCHv5 01/11] tap: add interface to get device fd Michael S. Tsirkin
2010-03-16 17:10 ` [Qemu-devel] [PATCHv5 02/11] kvm: add API to set ioeventfd Michael S. Tsirkin
2010-03-16 17:10 ` [Qemu-devel] [PATCHv5 03/11] notifier: event notifier implementation Michael S. Tsirkin
2010-03-16 17:10 ` [Qemu-devel] [PATCHv5 04/11] virtio: notifier support + APIs for queue fields Michael S. Tsirkin
2010-03-17  4:14   ` Amit Shah [this message]
2010-03-17 10:48     ` [Qemu-devel] " Michael S. Tsirkin
2010-03-16 17:11 ` [Qemu-devel] [PATCHv5 05/11] virtio: add set_status callback Michael S. Tsirkin
2010-03-16 17:11 ` [Qemu-devel] [PATCHv5 06/11] virtio: move typedef to qemu-common Michael S. Tsirkin
2010-03-16 17:11 ` [Qemu-devel] [PATCHv5 07/11] virtio-pci: fill in notifier support Michael S. Tsirkin
2010-03-16 17:11 ` [Qemu-devel] [PATCHv5 08/11] vhost: vhost net support Michael S. Tsirkin
2010-03-16 18:56   ` [Qemu-devel] " Juan Quintela
2010-03-16 17:11 ` [Qemu-devel] [PATCHv5 09/11] tap: add vhost/vhostfd options Michael S. Tsirkin
2010-03-16 17:11 ` [Qemu-devel] [PATCHv5 10/11] tap: add API to retrieve vhost net header Michael S. Tsirkin
2010-03-16 17:11 ` [Qemu-devel] [PATCHv5 11/11] virtio-net: vhost net support Michael S. Tsirkin
2010-03-16 18:57   ` [Qemu-devel] " Juan Quintela
2010-03-17 10:40     ` Michael S. Tsirkin
2010-03-16 18:58 ` [Qemu-devel] Re: [PATCHv5 00/11] vhost-net: upstream integration Juan Quintela
2010-03-17  4:14 ` Amit Shah

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=20100317041405.GD20122@amit-x200.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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;
as well as URLs for NNTP newsgroup(s).