From: Avi Kivity <avi@redhat.com>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: "'kvm@vger.kernel.org'" <kvm@vger.kernel.org>,
"'Mark McLoughlin'" <markmc@redhat.com>,
"'Marcelo Tosatti'" <mtosatti@redhat.com>
Subject: Re: [PATCH 0/8] kvm: fix device assignment hotplug
Date: Tue, 24 Feb 2009 12:08:48 +0200 [thread overview]
Message-ID: <49A3C730.2020705@redhat.com> (raw)
In-Reply-To: <715D42877B251141A38726ABF5CABF2C0195A1F9AF@pdsmsx503.ccr.corp.intel.com>
Han, Weidong wrote:
> Last qemu merge broke device assignment hotplug. It didn't call qemu_pci_hot_assign_device in pci_device_hot_add for device assignment hot add, and also missed device assignment hotplug command in pci_add command. This patchset fixes this issue. Note that this patchset rebases and includes the patches of fixing hot remove assigned device, which have been sent in mailing list for version 3.
>
Applied all, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-02-24 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 7:12 [PATCH 0/8] kvm: fix device assignment hotplug Han, Weidong
2009-02-24 10:08 ` 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=49A3C730.2020705@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mtosatti@redhat.com \
--cc=weidong.han@intel.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