From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] spapr: Clarify why DR connectors aren't user creatable
Date: Tue, 13 Oct 2020 11:39:07 +1100 [thread overview]
Message-ID: <20201013003907.GE71119@yekko.fritz.box> (raw)
In-Reply-To: <160250199940.765467.6896806997161856576.stgit@bahia.lan>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
On Mon, Oct 12, 2020 at 01:26:39PM +0200, Greg Kurz wrote:
> DR connector is a device that emulates a firmware abstraction used by PAPR
> compliant guests to manage hotplug/dynamic-reconfiguration of PHBs, PCI
> devices, memory, and CPUs.
>
> It is internally created by the spapr platform and requires to be owned by
> either the machine (PHBs, CPUs, memory) or by a PHB (PCI devices).
>
> Signed-off-by: Greg Kurz <groug@kaod.org>
Applied to ppc-for-5.2, thanks.
> ---
> hw/ppc/spapr_drc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/hw/ppc/spapr_drc.c b/hw/ppc/spapr_drc.c
> index 697b28c34305..77718cde1ff2 100644
> --- a/hw/ppc/spapr_drc.c
> +++ b/hw/ppc/spapr_drc.c
> @@ -586,7 +586,8 @@ static void spapr_dr_connector_class_init(ObjectClass *k, void *data)
> dk->realize = realize;
> dk->unrealize = unrealize;
> /*
> - * Reason: it crashes FIXME find and document the real reason
> + * Reason: DR connector needs to be wired to either the machine or to a
> + * PHB in spapr_dr_connector_new().
> */
> dk->user_creatable = false;
> }
>
>
--
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: 833 bytes --]
prev parent reply other threads:[~2020-10-13 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 11:26 [PATCH] spapr: Clarify why DR connectors aren't user creatable Greg Kurz
2020-10-13 0:39 ` David Gibson [this message]
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=20201013003907.GE71119@yekko.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--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).