From: Sasha Levin <levinsasha928@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Asias He <asias.hejun@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Prasad Joshi <prasadjoshi124@gmail.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH 3/3] kvm tools: Make virtio-blk kvm__irq_line thread safe
Date: Fri, 29 Apr 2011 11:29:40 +0300 [thread overview]
Message-ID: <1304065780.10069.19.camel@lappy> (raw)
In-Reply-To: <BANLkTikyUnAne+waUCTGUkq-JEp6Nxn_Xw@mail.gmail.com>
On Fri, 2011-04-29 at 10:55 +0300, Pekka Enberg wrote:
> On Fri, Apr 29, 2011 at 10:26 AM, Asias He <asias.hejun@gmail.com> wrote:
> >> Yes, looks strange. Asias, did you see some bad behavior that this
> >> fixes?
> >
> > Yes. I see random virtio net hangs with scp test. This commit
> > 847838c573f4c04be7547f508a99be2dfdefb4fd triggers this problem as we are
> > using separte irq lines for each virtio devices instead of sharing one
> > irq line for all virtio devices.
>
> That's interesting. So reverting that commit makes the hangs go away?
I was able to reproduce the hang by running 'ping -f' from the guest to
the host and from the host to the guest.
>From debugging I found that virtio-net's VIRTIO_PCI_QUEUE_NOTIFY doesn't
get called once it's hung.
The hang does seems to go away once I revert
847838c573f4c04be7547f508a99be2dfdefb4fd .
--
Sasha.
next prev parent reply other threads:[~2011-04-29 8:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 6:36 [PATCH 1/3] kvm tools: Make virtio-net kvm__irq_line thread safe Asias He
2011-04-29 6:36 ` [PATCH 2/3] kvm tools: Make virtio-console " Asias He
2011-04-29 6:44 ` Ingo Molnar
2011-04-29 6:36 ` [PATCH 3/3] kvm tools: Make virtio-blk " Asias He
2011-04-29 6:44 ` Ingo Molnar
2011-04-29 6:55 ` Pekka Enberg
2011-04-29 7:26 ` Asias He
2011-04-29 7:55 ` Pekka Enberg
2011-04-29 8:29 ` Sasha Levin [this message]
2011-04-29 6:46 ` [PATCH 1/3] kvm tools: Make virtio-net " Ingo Molnar
2011-04-29 6:52 ` Pekka Enberg
2011-04-29 7:13 ` Asias He
2011-04-29 7:15 ` Pekka Enberg
2011-04-29 7:38 ` Asias He
2011-04-29 7:45 ` Ingo Molnar
2011-04-29 7:53 ` Sasha Levin
2011-04-29 10:02 ` Cyrill Gorcunov
2011-04-29 10:37 ` Pekka Enberg
2011-04-29 10:47 ` Cyrill Gorcunov
2011-04-29 10:22 ` Ingo Molnar
2011-04-29 16:52 ` Sasha Levin
2011-04-29 20:39 ` Ingo Molnar
2011-04-29 7:30 ` Ingo Molnar
2011-04-29 7:47 ` Asias He
2011-04-29 10:32 ` Ingo Molnar
2011-04-29 10:42 ` Pekka Enberg
2011-04-29 17:43 ` Pekka Enberg
2011-04-29 19:59 ` Ingo Molnar
2011-04-30 7:44 ` Pekka Enberg
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=1304065780.10069.19.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.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.