All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio/ringtest: fix up need_event math
Date: Fri, 27 Oct 2017 16:16:37 +0300	[thread overview]
Message-ID: <20171027161336-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20171026103647.588ac89b.cohuck@redhat.com>

On Thu, Oct 26, 2017 at 10:36:47AM +0200, Cornelia Huck wrote:
> On Thu, 26 Oct 2017 04:48:01 +0300
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > last kicked event index must be updated unconditionally:
> > even if we don't need to kick, we do not want to re-check
> > the same entry for events.
> > 
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> >  tools/virtio/ringtest/ring.c | 24 +++++++++++++++---------
> >  1 file changed, 15 insertions(+), 9 deletions(-)
> 
> Acked-by: Cornelia Huck <cohuck@redhat.com>

Actually it seems to sometimes trigger stalls when host and guest
are on the same physical core. To trigger:

./ring --sleep --host-affinity 0 --guest-affinity 0

This worries me since it's similar to what vhost does.

Still debugging - anyone see anything suspicious?


> I think virtio_ring_0_9 has the same issue?

I think it does, posted a patch.

-- 
MST

  reply	other threads:[~2017-10-27 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26  1:48 [PATCH] virtio/ringtest: fix up need_event math Michael S. Tsirkin
2017-10-26  8:36 ` Cornelia Huck
2017-10-27 13:16   ` Michael S. Tsirkin [this message]
2017-10-26  8:36 ` Cornelia Huck
2017-10-26 12:28 ` Jason Wang
2017-10-26 12:28 ` Jason Wang
  -- strict thread matches above, loose matches on Subject: below --
2017-10-26  1:48 Michael S. Tsirkin

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=20171027161336-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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 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.