From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: mdroth@linux.vnet.ibm.com, sursingh@redhat.com,
qemu-devel@nongnu.org, groug@kaod.org, qemu-ppc@nongnu.org,
bharata@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 0/6] spapr: DRC cleanups (part IV)
Date: Fri, 16 Jun 2017 12:00:31 +0800 [thread overview]
Message-ID: <20170616040031.GE30484@umbus> (raw)
In-Reply-To: <4f1e9592-566f-b558-91e8-e39ac8691455@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]
On Thu, Jun 15, 2017 at 07:10:55PM +0200, Laurent Vivier wrote:
> On 08/06/2017 07:09, David Gibson wrote:
> > This fourth isntallment of cleanups to the DRC code introduces the
> > first changes to the fundamental state handling. We change the
> > initial states in the reset code and attach code for PCI devices, and
> > are able to remove the 'signalled' state variable with those fixes.
> >
> > There are also some more mechanical cleanups in preparation for
> > further cleanups and fixes to the state management.
> >
> > David Gibson (6):
> > spapr: Start hotplugged PCI devices in ISOLATED state
> > spapr: Eliminate DRC 'signalled' state variable
> > spapr: Split DRC release from DRC detach
> > spapr: Make DRC reset force DRC into known state
> > spapr: Clean up DRC set_allocation_state path
> > spapr: Clean up DRC set_isolation_state() path
> >
> > hw/ppc/spapr.c | 15 --
> > hw/ppc/spapr_drc.c | 363 +++++++++++++++++++++++----------------------
> > hw/ppc/spapr_events.c | 10 --
> > include/hw/ppc/spapr_drc.h | 10 +-
> > 4 files changed, 188 insertions(+), 210 deletions(-)
> >
>
> I've tested your series rebased on master.
>
> - plugging a CPU while the OS is not started (stopped in SLOF/GRUB):
>
> The cpu can be hotplugged, but once the OS is started, the OS
> doesn't detect it and it can't be unplugged.
>
> - plugging a memory DIMM while the OS is not started:
>
> The first device_del does nothing, the second one crashes qemu
>
> - migration with hotplugged cpu (with OS started):
>
> CPU cannot be unplugged on destination side
>
> - migration with hotplugged memory DIMM (with OS started):
>
> The first device_del does nothing, the second one crashes qemu
>
> As it's cleanup, I guess this is what is expected
> (the results are the same as before cleanup series).
Right, I wouldn't expect this series to fix problems yet - it just
makes the code clearer so it will be easier to do so in future.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-06-16 4:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 5:09 [Qemu-devel] [PATCH 0/6] spapr: DRC cleanups (part IV) David Gibson
2017-06-08 5:09 ` [Qemu-devel] [PATCH 1/6] spapr: Start hotplugged PCI devices in ISOLATED state David Gibson
2017-06-19 10:11 ` Greg Kurz
2017-06-08 5:09 ` [Qemu-devel] [PATCH 2/6] spapr: Eliminate DRC 'signalled' state variable David Gibson
2017-06-19 10:12 ` Greg Kurz
2017-06-08 5:09 ` [Qemu-devel] [PATCH 3/6] spapr: Split DRC release from DRC detach David Gibson
2017-06-19 10:14 ` Greg Kurz
2017-06-08 5:09 ` [Qemu-devel] [PATCH 4/6] spapr: Make DRC reset force DRC into known state David Gibson
2017-06-19 10:25 ` Greg Kurz
2017-06-20 8:23 ` Bharata B Rao
2017-06-21 7:24 ` David Gibson
2017-06-08 5:09 ` [Qemu-devel] [PATCH 5/6] spapr: Clean up DRC set_allocation_state path David Gibson
2017-06-19 12:09 ` Greg Kurz
2017-06-08 5:09 ` [Qemu-devel] [PATCH 6/6] spapr: Clean up DRC set_isolation_state() path David Gibson
2017-06-19 13:16 ` Greg Kurz
2017-06-19 22:52 ` Michael Roth
2017-06-20 1:12 ` David Gibson
2017-06-15 17:10 ` [Qemu-devel] [PATCH 0/6] spapr: DRC cleanups (part IV) Laurent Vivier
2017-06-16 4:00 ` David Gibson [this message]
2017-06-16 7:57 ` Alexey Kardashevskiy
2017-06-19 19:51 ` David Gibson
2017-06-19 22:52 ` Michael Roth
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=20170616040031.GE30484@umbus \
--to=david@gibson.dropbear.id.au \
--cc=bharata@linux.vnet.ibm.com \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sursingh@redhat.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).