From: David Gibson <david@gibson.dropbear.id.au>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: imammedo@redhat.com, agraf@suse.de, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Correctly set query_hotpluggable_cpus hook based on machine version
Date: Mon, 8 Aug 2016 10:09:44 +1000 [thread overview]
Message-ID: <20160808000944.GM9189@voom.fritz.box> (raw)
In-Reply-To: <20160805145159.GA8994@in.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]
On Fri, Aug 05, 2016 at 08:21:59PM +0530, Bharata B Rao wrote:
> On Fri, Aug 05, 2016 at 05:50:29PM +1000, David Gibson wrote:
> > Prior to c8721d3 "spapr: Error out when CPU hotplug is attempted on older
> > pseries machines", attempting to use query-hotpluggable-cpus on pseries-2.6
> > and earlier machine types would SEGV.
> >
> > That change fixed that, but due to some unexpected interactions in init
> > order and a brown-paper-bag worthy failure to test, it accidentally
> > disabled query-hotpluggable-cpus for all pseries machine types, including
> > the current one which should allow it.
> >
> > In fact, query_hotpluggable_cpus needs to be non-NULL when and only when
> > the dr_cpu_enabled flag in sPAPRMachineClass is set, which makes
> > dr_cpu_enabled itself redundant.
> >
> > This patch removes dr_cpu_enabled, instead directly setting
> > query_hotpluggable_cpus from the machine class_init functions, and using
> > that to determine the availability of CPU hotplug when necessary.
>
> dr_cpu_enabled actually determines if CPU hotplug feature is present
> or not. It also controls the creation of DRC-specific properties
> in /cpus DT node like ibm,drc-indexes etc
>
> query_hotpluggable_cpus just tells us if the machine supports the
> querying of hotpluggable CPUS. query_hotpluggable_cpus definitely
> implies dr_cpu_enabled but dr_cpu_enabled can exist on its own
> (theoretically at the least) without query_hotpluggable_cpus.
Um, so that certainly can't happen in practice. Just like
query_hotpluggable_cpus, dr_cpu_enabled is set for pseries-2.7 and no
earlier machine types. There's no way to override it in
configuration.
And even in theory I can't see how dr_cpu_enabled could make any sense
without query_hotpluggable_cpus. The whole hotplug infrastructure is
based around the core objects, which don't exist with the earlier
machine types.
> So I think we should not replace dr_cpu_enabled with query_hotpluggable_cpus.
>
> However, I tested this patch and it works as intended.
>
> Regards,
> Bharata.
>
--
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:[~2016-08-08 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 7:50 [Qemu-devel] [PATCH] spapr: Correctly set query_hotpluggable_cpus hook based on machine version David Gibson
2016-08-05 14:51 ` Bharata B Rao
2016-08-08 0:09 ` David Gibson [this message]
2016-08-08 8:46 ` Igor Mammedov
2016-08-09 0:12 ` David Gibson
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=20160808000944.GM9189@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).