From: Sheng Yang <sheng@linux.intel.com>
To: kvm@vger.kernel.org
Cc: Avi Kivity <avi@redhat.com>,
armbru@redhat.com, Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: Device assignment hotplug broken
Date: Tue, 30 Jun 2009 13:38:52 +0800 [thread overview]
Message-ID: <200906301338.52915.sheng@linux.intel.com> (raw)
In-Reply-To: <4A43B2B3.1040204@redhat.com>
On Friday 26 June 2009 01:24:03 Avi Kivity wrote:
> The impact of the hotplug changes on device assignment were too
> difficult for me to fix up during the merge, so I disabled it
> temporarily. Please take a look at qemu-kvm.git commit a3b371477e3.
When the device assignment can come back? 4 day passed and no message from
Markus Armbruster till now.
--
regards
Yang, Sheng
next prev parent reply other threads:[~2009-06-30 5:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 17:24 Device assignment hotplug broken Avi Kivity
2009-06-30 5:38 ` Sheng Yang [this message]
2009-06-30 12:28 ` Markus Armbruster
2009-07-01 1:54 ` Sheng Yang
2009-07-01 15:45 ` Markus Armbruster
2009-07-01 16:22 ` [PATCH] Fix up device assignment hotplug and re-enable it Markus Armbruster
2009-07-02 12:03 ` Avi Kivity
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=200906301338.52915.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox