From: Yuval Shaia <yuval.shaia@oracle.com>
To: Yanjun Zhu <yanjun.zhu@oracle.com>
Cc: mst@redhat.com, linux-rdma@vger.kernel.org, cohuck@redhat.com,
qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org,
jgg@mellanox.com
Subject: Re: [RFC 3/3] RDMA/virtio-rdma: VirtIO rdma driver
Date: Sun, 14 Apr 2019 08:20:25 +0300 [thread overview]
Message-ID: <20190414052024.GA2842@lap1> (raw)
In-Reply-To: <199a70a8-5926-66af-d2d7-b19a0a0f46a2@oracle.com>
> > +
> > + wake_up(&dev->acked);
> > +
> > + printk("%s\n", __func__);
>
> Cool:-)
>
> this line should be for debug?
Yes
>
> Zhu Yanjun
>
WARNING: multiple messages have this Message-ID (diff)
From: Yuval Shaia <yuval.shaia@oracle.com>
To: Yanjun Zhu <yanjun.zhu@oracle.com>
Cc: virtualization@lists.linux-foundation.org, qemu-devel@nongnu.org,
mst@redhat.com, cohuck@redhat.com, marcel.apfelbaum@gmail.com,
linux-rdma@vger.kernel.org, jgg@mellanox.com
Subject: Re: [Qemu-devel] [RFC 3/3] RDMA/virtio-rdma: VirtIO rdma driver
Date: Sun, 14 Apr 2019 08:20:25 +0300 [thread overview]
Message-ID: <20190414052024.GA2842@lap1> (raw)
In-Reply-To: <199a70a8-5926-66af-d2d7-b19a0a0f46a2@oracle.com>
> > +
> > + wake_up(&dev->acked);
> > +
> > + printk("%s\n", __func__);
>
> Cool:-)
>
> this line should be for debug?
Yes
>
> Zhu Yanjun
>
WARNING: multiple messages have this Message-ID (diff)
From: Yuval Shaia <yuval.shaia@oracle.com>
To: Yanjun Zhu <yanjun.zhu@oracle.com>
Cc: mst@redhat.com, linux-rdma@vger.kernel.org, cohuck@redhat.com,
qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org,
jgg@mellanox.com
Subject: Re: [Qemu-devel] [RFC 3/3] RDMA/virtio-rdma: VirtIO rdma driver
Date: Sun, 14 Apr 2019 08:20:25 +0300 [thread overview]
Message-ID: <20190414052024.GA2842@lap1> (raw)
Message-ID: <20190414052025.mtMhfHJ0TI17OAQ-D6Pw8kW2Zj6xdbBbXxrJzk75dLk@z> (raw)
In-Reply-To: <199a70a8-5926-66af-d2d7-b19a0a0f46a2@oracle.com>
> > +
> > + wake_up(&dev->acked);
> > +
> > + printk("%s\n", __func__);
>
> Cool:-)
>
> this line should be for debug?
Yes
>
> Zhu Yanjun
>
next prev parent reply other threads:[~2019-04-14 5:20 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 11:01 [RFC 0/3] VirtIO RDMA Yuval Shaia
2019-04-11 11:01 ` [Qemu-devel] " Yuval Shaia
2019-04-11 11:01 ` [RFC 1/3] virtio-net: Move some virtio-net-pci decl to include/hw/virtio Yuval Shaia
2019-04-11 11:01 ` [Qemu-devel] " Yuval Shaia
2019-04-11 11:01 ` Yuval Shaia
2019-04-11 11:01 ` [RFC 2/3] hw/virtio-rdma: VirtIO rdma device Yuval Shaia
2019-04-11 11:01 ` [Qemu-devel] " Yuval Shaia
2019-04-19 23:20 ` Michael S. Tsirkin
2019-04-19 23:20 ` [Qemu-devel] " Michael S. Tsirkin
2019-04-19 23:20 ` Michael S. Tsirkin
2019-04-23 7:59 ` Cornelia Huck
2019-04-23 7:59 ` [Qemu-devel] " Cornelia Huck
2019-04-23 7:59 ` Cornelia Huck
2019-04-11 11:01 ` Yuval Shaia
2019-04-11 11:01 ` [RFC 3/3] RDMA/virtio-rdma: VirtIO rdma driver Yuval Shaia
2019-04-11 11:01 ` Yuval Shaia
2019-04-11 11:01 ` [Qemu-devel] " Yuval Shaia
2019-04-13 7:58 ` Yanjun Zhu
2019-04-13 7:58 ` [Qemu-devel] " Yanjun Zhu
2019-04-14 5:20 ` Yuval Shaia [this message]
2019-04-14 5:20 ` Yuval Shaia
2019-04-14 5:20 ` Yuval Shaia
2019-04-14 5:20 ` Yuval Shaia
2019-04-13 7:58 ` Yanjun Zhu
2019-04-16 1:07 ` Bart Van Assche
2019-04-16 1:07 ` [Qemu-devel] " Bart Van Assche
2019-04-16 8:56 ` Yuval Shaia
2019-04-16 8:56 ` Yuval Shaia
2019-04-16 8:56 ` [Qemu-devel] " Yuval Shaia
2019-04-16 8:56 ` Yuval Shaia
2019-04-11 17:02 ` [RFC 0/3] VirtIO RDMA Cornelia Huck
2019-04-11 17:02 ` [Qemu-devel] " Cornelia Huck
2019-04-11 17:02 ` Cornelia Huck
2019-04-11 17:24 ` Jason Gunthorpe
2019-04-11 17:24 ` Jason Gunthorpe
2019-04-11 17:24 ` [Qemu-devel] " Jason Gunthorpe
2019-04-11 17:24 ` Jason Gunthorpe
2019-04-11 17:34 ` Yuval Shaia
2019-04-11 17:34 ` [Qemu-devel] " Yuval Shaia
2019-04-11 17:34 ` Yuval Shaia
2019-04-11 17:40 ` Jason Gunthorpe
2019-04-11 17:40 ` [Qemu-devel] " Jason Gunthorpe
2019-04-11 17:40 ` Jason Gunthorpe
2019-04-15 10:04 ` Yuval Shaia
2019-04-15 10:04 ` [Qemu-devel] " Yuval Shaia
2019-04-15 10:04 ` Yuval Shaia
2019-04-15 10:04 ` Yuval Shaia
2019-04-11 17:40 ` Jason Gunthorpe
2019-04-11 17:41 ` Yuval Shaia
2019-04-11 17:41 ` [Qemu-devel] " Yuval Shaia
2019-04-11 17:41 ` Yuval Shaia
2019-04-12 9:51 ` Devesh Sharma via Qemu-devel
2019-04-12 9:51 ` [Qemu-devel] " Devesh Sharma via Qemu-devel
2019-04-12 9:51 ` Devesh Sharma
2019-04-15 10:27 ` Yuval Shaia
2019-04-15 10:27 ` Yuval Shaia
2019-04-15 10:27 ` [Qemu-devel] " Yuval Shaia
2019-04-15 10:27 ` Yuval Shaia
2019-04-11 17:41 ` Yuval Shaia
2019-04-11 17:34 ` Yuval Shaia
2019-04-15 10:35 ` Yuval Shaia
2019-04-15 10:35 ` Yuval Shaia
2019-04-15 10:35 ` [Qemu-devel] " Yuval Shaia
2019-04-15 10:35 ` Yuval Shaia
2019-04-19 11:16 ` Hannes Reinecke
2019-04-19 11:16 ` Hannes Reinecke
2019-04-19 11:16 ` Hannes Reinecke
2019-04-22 6:00 ` Leon Romanovsky
2019-04-22 6:00 ` Leon Romanovsky
2019-04-30 17:16 ` Yuval Shaia
2019-04-30 17:16 ` Yuval Shaia
2019-04-30 17:16 ` Yuval Shaia
2019-04-22 16:45 ` Jason Gunthorpe
2019-04-22 16:45 ` Jason Gunthorpe
2019-04-30 17:13 ` Yuval Shaia
2019-04-30 17:13 ` Yuval Shaia
2019-04-30 17:13 ` Yuval Shaia
2019-04-30 17:13 ` Yuval Shaia
2019-05-07 19:43 ` Jason Gunthorpe
2019-05-07 19:43 ` Jason Gunthorpe
2019-04-30 12:16 ` Yuval Shaia
2019-04-30 12:16 ` Yuval Shaia
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=20190414052024.GA2842@lap1 \
--to=yuval.shaia@oracle.com \
--cc=cohuck@redhat.com \
--cc=jgg@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=yanjun.zhu@oracle.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 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.