From: Avi Kivity <avi@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: Loss of lock drop in qemu/net.c
Date: Wed, 17 Dec 2008 11:39:40 +0200 [thread overview]
Message-ID: <4948C8DC.9050408@redhat.com> (raw)
In-Reply-To: <1229505563.3685.37.camel@localhost.localdomain>
Mark McLoughlin wrote:
> On Tue, 2008-12-16 at 21:38 +0200, Avi Kivity wrote:
>
>> The recent qemu merged does not allow net.h to include kvm code (due to
>> a dependency on cpu.h). This means I had to drop the
>> kvm_sleep_begin()/kvm_sleep_end() around the packet send (which, btw,
>> makes the whole thing vulnerable to hotunplug; we need refcounting or
>> locking here).
>>
>
> How can the tap vlan client be affected by hotunplug?
>
It cannot; my mistake.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-12-17 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 19:38 Loss of lock drop in qemu/net.c Avi Kivity
2008-12-16 20:25 ` Anthony Liguori
2008-12-17 9:38 ` Avi Kivity
2008-12-17 9:19 ` Mark McLoughlin
2008-12-17 9:39 ` Avi Kivity [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=4948C8DC.9050408@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=markmc@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