From: Marcel Apfelbaum <marcel@redhat.com>
To: "Ouyang, Changchun" <changchun.ouyang@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Qemu-devel Digest, Vol 149, Issue 266
Date: Thu, 13 Aug 2015 11:41:11 +0300 [thread overview]
Message-ID: <55CC5827.80802@redhat.com> (raw)
In-Reply-To: <F52918179C57134FAEC9EA62FA2F962511CB7447@shsmsx102.ccr.corp.intel.com>
On 08/13/2015 08:32 AM, Ouyang, Changchun wrote:
>
>
>> -----Original Message-----
>> Date: Wed, 12 Aug 2015 14:15:54 +0300
>> From: "Michael S. Tsirkin" <mst@redhat.com>
>> To: Marcel Apfelbaum <marcel@redhat.com>
>> Cc: qemu-devel@nongnu.org
>> Subject: Re: [Qemu-devel] [PATCH] virtio/vhost: drop unnecessary
>> VHOST_SET_VRING call
>> Message-ID: <20150812141448-mutt-send-email-mst@redhat.com>
>> Content-Type: text/plain; charset=us-ascii
>>
>> On Wed, Aug 12, 2015 at 02:10:56PM +0300, Marcel Apfelbaum wrote:
>>> On 08/12/2015 01:34 PM, Michael S. Tsirkin wrote:
>>>> On Wed, Aug 12, 2015 at 01:19:51PM +0300, Marcel Apfelbaum wrote:
>>>>> No need to send VHOST_SET_VRING_CALL to backend before the
>>>>> negotiation with the guest is finished.
>>>>>
>>>>> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
>>>>
>>>> Well - we do need to set it to the masked notifier initially to avoid
>>>> losing events. You can't just drop it - need to move this call
>>>> somewhere else.
>
> Agree with m.s.t.
> We could not drop it.
> Vhost-user multi queue also need this.
I'll try to call it a little bit later instead of dropping it.
Thanks,
Marcel
>
>>> What do we need to set?
>>> I just dropped the call to VHOST_SET_VRING_CALL.
>>>
>>> Thanks,
>>> Marcel
>>
>> We use two eventfds: masked and unmasked one.
>> We switch dynamically dependent on msi mask value.
>> Code assumes we start out masked, so we need to match that.
>>
>>
>>>>
>>>>> ---
>>>>> hw/virtio/vhost.c | 13 +------------
>>>>> 1 file changed, 1 insertion(+), 12 deletions(-)
>>>>>
>>>>> diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c index
>>>>> 2712c6f..b448542 100644
>>>>> --- a/hw/virtio/vhost.c
>>>>> +++ b/hw/virtio/vhost.c
>>>>> @@ -875,24 +875,13 @@ static void
>> vhost_eventfd_del(MemoryListener
>>>>> *listener,
>>>>> static int vhost_virtqueue_init(struct vhost_dev *dev,
>>>>> struct vhost_virtqueue *vq, int n)
>>>>> {
>>>>> - struct vhost_vring_file file = {
>>>>> - .index = n,
>>>>> - };
>>>>> int r = event_notifier_init(&vq->masked_notifier, 0);
>>>>> +
>>>>> if (r < 0) {
>>>>> return r;
>>>>> }
>>>>>
>>>>> - file.fd = event_notifier_get_fd(&vq->masked_notifier);
>>>>> - r = dev->vhost_ops->vhost_call(dev, VHOST_SET_VRING_CALL, &file);
>>>>> - if (r) {
>>>>> - r = -errno;
>>>>> - goto fail_call;
>>>>> - }
>>>>> return 0;
>>>>> -fail_call:
>>>>> - event_notifier_cleanup(&vq->masked_notifier);
>>>>> - return r;
>>>>> }
>>>>>
>>>>> static void vhost_virtqueue_cleanup(struct vhost_virtqueue *vq)
>>>>> --
>>>>> 2.1.0
>>
>>
prev parent reply other threads:[~2015-08-13 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.116842.1439380262.903.qemu-devel@nongnu.org>
2015-08-13 5:32 ` [Qemu-devel] Qemu-devel Digest, Vol 149, Issue 266 Ouyang, Changchun
2015-08-13 8:41 ` Marcel Apfelbaum [this message]
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=55CC5827.80802@redhat.com \
--to=marcel@redhat.com \
--cc=changchun.ouyang@intel.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).