qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Corey Minyard <cminyard@mvista.com>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ppc/pnv: restrict BMC object to the BMC simulator
Date: Mon, 1 May 2017 14:45:47 +1000	[thread overview]
Message-ID: <20170501044547.GG13773@umbus.fritz.box> (raw)
In-Reply-To: <1493367991-21269-1-git-send-email-clg@kaod.org>

[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]

On Fri, Apr 28, 2017 at 10:26:31AM +0200, Cédric Le Goater wrote:
> Today, when a PowerNV guest runs, it uses the sensor definitions of
> the BMC simulator to populate the device tree. But an external IPMI
> BMC could also be used and, in that case, it is not (yet) possible to
> retrieve the sensor list. Generating the OEM SEL event for shutdown or
> reboot also does not make sense as it should be generated on the BMC
> side.
> 
> This change allows a guest to use an 'ipmi-bmc-extern' backend to the
> 'isa-ipmi-bt' device and a 'chardev' for transport such as :
>  
> 	-chardev socket,id=ipmi0,host=localhost,port=9002,reconnect=10 \
> 	-device ipmi-bmc-extern,id=bmc0,chardev=ipmi0 \
> 	-device isa-ipmi-bt,bmc=bmc0,irq=10
> 
> and connect to a BMC simulator, the OpenIPMI ipmi_sim simulator for
> instance.
> 
> Signed-off-by: Cédric Le Goater <clg@kaod.org>

Applied to ppc-for-2.10.

> ---
> 
>  Corey,
> 
>  Should we externalize the TYPE_IPMI_BMC_EXTERN and TYPE_IPMI_BMC_SIMULATOR
>  defines ?

That's a good question, though.  My inclination would be yes.

> 
>  hw/ppc/pnv.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: qemu-powernv-2.10.git/hw/ppc/pnv.c
> ===================================================================
> --- qemu-powernv-2.10.git.orig/hw/ppc/pnv.c
> +++ qemu-powernv-2.10.git/hw/ppc/pnv.c
> @@ -520,7 +520,7 @@ static void ppc_powernv_reset(void)
>       * This is the internal simulator but it could also be an external
>       * BMC.
>       */
> -    obj = object_resolve_path_type("", TYPE_IPMI_BMC, NULL);
> +    obj = object_resolve_path_type("", "ipmi-bmc-sim", NULL);
>      if (obj) {
>          pnv->bmc = IPMI_BMC(obj);
>      }
> 

-- 
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 --]

      reply	other threads:[~2017-05-01  4:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  8:26 [Qemu-devel] [PATCH] ppc/pnv: restrict BMC object to the BMC simulator Cédric Le Goater
2017-05-01  4:45 ` 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=20170501044547.GG13773@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=clg@kaod.org \
    --cc=cminyard@mvista.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).