qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: blauwirbel@gmail.com, yamahata@valinux.co.jp,
	Alex Williamson <alex.williamson@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] About hotplug multifunction
Date: Fri, 9 Sep 2011 10:32:26 +0300	[thread overview]
Message-ID: <20110909073226.GB5593@redhat.com> (raw)
In-Reply-To: <1466280941.590770.1315552101666.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>

On Fri, Sep 09, 2011 at 03:08:21AM -0400, Amos Kong wrote:
> Hello all,
> 
> I'm working on hotplug pci multifunction. 
> 
> 1. qemu cmdline: 
> ./x86_64-softmmu/qemu-system-x86_64 -snapshot -m 2000 /home/kvm_autotest_root/images/rhel61-64-virtio.qcow2 -vnc :0 -monitor unix:/tmp/a,server,nowait --enable-kvm -net none
> 
> 2. script to add virtio-blk devices:
> for i in `seq 1 7` 0;do
> qemu-img create /tmp/resize$i.qcow2 1G -f qcow2
> echo drive_add 0x6.$i id=drv$i,if=none,file=/tmp/resize$i.qcow2 | nc -U /tmp/a
> echo device_add virtio-blk-pci,id=dev$i,drive=drv$i,addr=0x6.$i,multifunction=on | nc -U /tmp/a
> done
> 
> 3. script to add virio-nic devices:
> for i in `seq 1 7` 0;do
> echo netdev_add tap,id=drv$i | nc -U /tmp/a
> echo device_add virtio-net-pci,id=dev$i,netdev=drv$i,addr=0x6.$i,multifunction=on | nc -U /tmp/a
> done
> 
> 4. current qemu behaviors
> 4.1. add func 1~7 one by one, then add func 0
> virtio-nic : success, all funcs are added
> virtio-blk : success
> 
> 4.2. add func 0~7 one by one
> virtio-nic : failed, only func 0 is added
> virtio-blk : success
> 
> 4.3. removing any single func in monitor
> virtio-nic: func 0 are not found in 'lspci', func 1~7 also exist. eth1~eth7 also exist.
> virtio-blk: func 0 are not found in 'lspci', func 1~7 also exist. the device. /dev/vda disappears,
>               vdb,vdc,vde,vdf,vdg,vdh,vdi,vdj also exist. If I re-add 8 funcs to guest, they all works.
>               # lspci (00:06.1 ~ 00:06.7 exist, 00:06.0 doesn't exit)
>               00:06.1 SCSI storage controller: Red Hat, Inc Virtio block device (rev ff)

something I noted when readin our acpi code:
we currently pass eject request for function 0 only:
               Name (_ADR, nr##0000)
We either need a device per function there (acpi 1.0),
send eject request for them all, or use ffff
as function number (newer acpi, not sure which version).
Need to see which guests (windows,linux) can handle which form.

> 
> qemu sends an acpi event to guest, then guest will remove all funcs in the slot.
> linux-2.6/drivers/pci/hotplug/acpiphp_glue.c:
> static int disable_device(struct acpiphp_slot *slot) {
>     list_for_each_entry(func, &slot->funcs, sibling) {
>         ...
> 
> Questions:
> 1. why func1~7 still can be found after hot-remove? is it same as real hardware?
> 2. why the func 1~7 could not be added to guest (addingfunc 0~7 one by one)?
> 3. how about this interface to hotplug/hot-unplug multifunction:
>    1) Add func 1-7 by monitor, add func 0, then send an acpi event to notice guest
>    2) Remove func0, send an acpi event to guest. (all funcs can be removed)

We must make sure guest acked removal of all functions. Surprise
removal would be bad.

> 4. what does "reversion 0xff" stand for?

You get ffffffff if no device responds to a configuration read.

-- 
MST

  reply	other threads:[~2011-09-09  7:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1749303074.590739.1315551830460.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2011-09-09  7:08 ` [Qemu-devel] About hotplug multifunction Amos Kong
2011-09-09  7:32   ` Michael S. Tsirkin [this message]
2011-09-09 17:05     ` Alex Williamson
2011-09-09 18:34       ` Marcelo Tosatti
2011-09-11  9:23         ` Michael S. Tsirkin
2011-09-11 15:01           ` Marcelo Tosatti
2011-09-11 18:51             ` Michael S. Tsirkin
2011-09-12 10:21               ` Marcelo Tosatti
2011-09-12 10:56                 ` Marcelo Tosatti
2011-09-12 12:24                   ` Michael S. Tsirkin
2011-09-13 12:23                     ` Amos Kong
2011-09-13 14:24                       ` Amos Kong
2011-09-09 17:43   ` Isaku Yamahata
2011-09-11  9:05     ` Michael S. Tsirkin
2011-09-13  5:57       ` Isaku Yamahata
2011-09-13  6:52         ` Gleb Natapov
2011-09-13  7:00           ` Isaku Yamahata
2011-09-13 10:00           ` Michael S. Tsirkin
2011-09-13 10:05           ` Michael S. Tsirkin
2011-09-13 10:05             ` Gleb Natapov
2011-11-23  9:06   ` Amos Kong

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=20110909073226.GB5593@redhat.com \
    --to=mst@redhat.com \
    --cc=akong@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /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;
as well as URLs for NNTP newsgroup(s).