qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "stefanha@gmail.com" <stefanha@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"afaerber@suse.de" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3 3/4] virtio-blk-test.c: add hotplug subtest
Date: Fri, 6 Jun 2014 18:10:49 +0800	[thread overview]
Message-ID: <20140606101049.GB12992@z.redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF1902086C06097@SZXEMA503-MBS.china.huawei.com>

On Fri, Jun 06, 2014 at 09:31:57AM +0000, Gonglei (Arei) wrote:
> > -----Original Message-----
> > From: Amos Kong [mailto:akong@redhat.com]
> > Sent: Friday, June 06, 2014 4:24 PM
> > To: Gonglei (Arei)
> > Cc: qemu-devel@nongnu.org; stefanha@gmail.com; afaerber@suse.de
> > Subject: Re: [PATCH v3 3/4] virtio-blk-test.c: add hotplug subtest
> > 
> > On Fri, Jun 06, 2014 at 08:05:15AM +0000, Gonglei (Arei) wrote:
> > > > -----Original Message-----
> > > > From: Amos Kong [mailto:akong@redhat.com]
> > > > Sent: Friday, June 06, 2014 1:29 PM
> > > > To: Gonglei (Arei)
> > > > Cc: qemu-devel@nongnu.org; stefanha@gmail.com; afaerber@suse.de
> > > > Subject: Re: [PATCH v3 3/4] virtio-blk-test.c: add hotplug subtest
> > > >
> > > > On Fri, Jun 06, 2014 at 01:28:59AM +0000, Gonglei (Arei) wrote:
> > > > > Hi, Amos
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Amos Kong [mailto:akong@redhat.com]
> > > > > > Sent: Friday, June 06, 2014 9:12 AM
> > > > > > To: qemu-devel@nongnu.org
> > > > > > Cc: stefanha@gmail.com; afaerber@suse.de; Gonglei (Arei)
> > > > > > Subject: [PATCH v3 3/4] virtio-blk-test.c: add hotplug subtest
> > > > > >
> > > > > > This patch adds a new subtest, it hotplugs 29 * 8 = 232 virtio-blk
> > > > > > devices to guest, and try to hot-unplug them.
> > > > > >
> > > > > > Note: the hot-unplug can't work without cooperation of guest OS.
> > > >
> > > >
> > > > > > +static void test_blk_hotplug(void)
> > > > > > +{
> > > > > > +    int i, j;
> > > > > > +
> > > > > > +    /* start with no network/block device, slots 3~0x1f are free */
> > > > > > +    qtest_start("-net none");
> > > > > > +
> > > > > > +    for (i = 3; i <= 0x1f; i++) {
> > > > > > +        for (j = 7; j >= 0; j--) {
> > > > > > +            qmp_exec_hmp_cmd("OK\r\n",
> > > > > > +                             "drive_add 0
> > > > > > if=none,file=/dev/null,id=drv-%x.%x",
> > > > > > +                             i, j);
> > > > > > +            qmp_exec_hmp_cmd("",
> > > > > > +                       "device_add
> > > > > > virtio-blk-pci,id=dev-%x.%x,drive=drv-%x.%x,"
> > > > > > +                       "addr=0x%x.%x,multifunction=on", i, j, i, j,
> > i,
> > > > j);
> > > > > > +        }
> > > > > > +    }
> > > > >
> > > > > Do the pci multifunction devices support hotplug/unplug yet?
> > > >
> > > > Yes.
> > > >
> > > > You can hotplug single functions one by one, guest will identify
> > > > all the functions when function 0 is added.
> > > > Hotunplug function 0, all functions in same slot will be removed.
> > > >
> > > Thanks.
> > >
> > > IMHO, if we hot-plug function 0 first, the other functions will be not support
> > to
> > > hot-plug.
> > 
> > Actually other functions can also be identified by guest, I had a
> > commit to add this support.
> > 
> > | commit f382a086f3129edc152b8044b69ccc6682e637bb
> > | Author: Amos Kong <akong@redhat.com>
> > | Date:   Fri Nov 25 15:03:07 2011 +0800
> > |
> > |     PCI: Can continually add funcs after adding func0
> > 
> > 
> Good, Thanks!
> 
> BTW, the limits of ACPI DSDT table have been resolved yet?

Which limit?

There was a hot-unplug bug of multiple function, I tried to
fix it by change ACPI DSDT table in seabios, but finally we
fixed this in kernel.

|commit ce29ca3ea40744f24c2b5d88431e8ac566d257cc
|Author: Amos Kong <kongjianjun@gmail.com>
|Date:   Wed May 23 10:20:35 2012 -0600
|
|    PCI: acpiphp: remove all functions in slot, even without ACPI _EJx

> > > Similarly, it will not be allowed if we only hot-unplug function 1~7,
> > > but function 0, right?
> > 
> > Yes. function 0 is always necessary.
> > 
> > > Best regards,
> > > -Gonglei
> > 
> > --
> > 			Amos.

-- 
			Amos.

  reply	other threads:[~2014-06-06 10:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  1:11 [Qemu-devel] [PATCH v3 0/4] test virtio-blk hotplug Amos Kong
2014-06-06  1:11 ` [Qemu-devel] [PATCH v3 1/4] virtio-blk-test.c: change pci_nop() to virtblk_init() Amos Kong
2014-06-06 13:20   ` Stefan Hajnoczi
2014-06-06  1:11 ` [Qemu-devel] [PATCH v3 2/4] qtest: introduce qmp_exec_hmp_cmd() Amos Kong
2014-06-06 13:20   ` Stefan Hajnoczi
2014-06-06  1:11 ` [Qemu-devel] [PATCH v3 3/4] virtio-blk-test.c: add hotplug subtest Amos Kong
2014-06-06  1:28   ` Gonglei (Arei)
2014-06-06  5:29     ` Amos Kong
2014-06-06  8:05       ` Gonglei (Arei)
2014-06-06  8:23         ` Amos Kong
2014-06-06  9:31           ` Gonglei (Arei)
2014-06-06 10:10             ` Amos Kong [this message]
2014-06-06 10:27               ` Gonglei (Arei)
2014-06-06 13:20   ` Stefan Hajnoczi
2014-06-06  1:12 ` [Qemu-devel] [PATCH v3 4/4] qtest: use qmp_exec_hmp_cmd() in blockdev-test Amos Kong
2014-06-06 13:21   ` Stefan Hajnoczi

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=20140606101049.GB12992@z.redhat.com \
    --to=akong@redhat.com \
    --cc=afaerber@suse.de \
    --cc=arei.gonglei@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).