From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/3] [PATCH] unregister pci device
Date: Thu, 27 Mar 2008 13:43:25 +0200 [thread overview]
Message-ID: <47EB885D.6000008@qumranet.com> (raw)
In-Reply-To: <47EB87AF.6060204@redhat.com>
Glauber Costa wrote:
> Avi Kivity wrote:
>> Glauber Costa wrote:
>>> If we fail after we have allocated the pci device, we have
>>> to get rid of it. Otherwise, a bogus device will be found on
>>> the bus
>>>
>>
>> Maybe, alter the order so the device is registered last thing. This
>> may help avoid races with pci passthrough hotplug.
>>
> That's the first thing I thought, but it makes things much more
> complicated. If really deserved, I can try again.
I don't think it's that critical at this stage.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2008-03-27 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 21:09 [PATCH 0/3] fixups for pci passthrough Glauber Costa
2008-03-26 21:09 ` [PATCH 1/3] [PATCH] passthrough Glauber Costa
2008-03-27 7:49 ` Avi Kivity
2008-03-26 21:09 ` [PATCH 2/3] [PATCH] unregister pci device Glauber Costa
2008-03-27 7:50 ` Avi Kivity
2008-03-27 11:40 ` Glauber Costa
2008-03-27 11:43 ` Avi Kivity [this message]
2008-03-26 21:09 ` [PATCH 3/3] [PATCH] remove warnings Glauber Costa
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=47EB885D.6000008@qumranet.com \
--to=avi@qumranet.com \
--cc=gcosta@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
/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