qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: Corey Minyard <cminyard@mvista.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 02/17] ipmi: Add a PC ISA type structure
Date: Mon, 11 May 2015 14:58:46 -0500	[thread overview]
Message-ID: <555109F6.9020108@acm.org> (raw)
In-Reply-To: <5551063B.2030708@redhat.com>

On 05/11/2015 02:42 PM, Paolo Bonzini wrote:
>
> On 11/05/2015 19:26, Andreas Färber wrote:
>> Another problem is that you're using object_new() in realize at all,
>> which means that it's too late for any management interface to tweak
>> properties on the new device. One possible solution would be to create
>> the object in a property setter, before realizing the object. Did you
>> look at how some of the other backends are implemented, such as rng?
> Note that this is not exactly a backend.  It's a different guest-visible
> I/O interface.  But there are no properties on the interface, so it's
> okay to create it at realize time.
>
> Paolo
I've debated this in my mind since I've been learning more about qemu. 
Some of
the bmc properties are being passed in to the interface and passed on to
the bmc.
Plus some IPMI systems have multiple interfaces that point to the same
bmc.  It
might be best to have the user create a bmc device then tie an interface
device to it.

If I do this, what is the acceptable way to look up another object this
way?  I hunted
a bit and didn't come up with anything clean.

Thanks,

-corey

  reply	other threads:[~2015-05-11 19:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 22:57 [Qemu-devel] [PATCH 00/17] Update to adding an IPMI device to qemu minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 01/17] Add a base IPMI interface minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 02/17] ipmi: Add a PC ISA type structure minyard
2015-04-26  8:58   ` Michael S. Tsirkin
2015-04-26  9:07     ` Michael S. Tsirkin
2015-05-08 21:16     ` Corey Minyard
2015-05-11 14:21       ` Paolo Bonzini
2015-05-11 17:26       ` Andreas Färber
2015-05-11 19:42         ` Paolo Bonzini
2015-05-11 19:58           ` Corey Minyard [this message]
2015-05-13 14:52             ` Paolo Bonzini
2015-05-16  1:48               ` Corey Minyard
2015-05-16 13:47                 ` Paolo Bonzini
2015-04-26  9:05   ` Michael S. Tsirkin
2015-04-26 17:03     ` Paolo Bonzini
2015-05-08 20:59       ` Corey Minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 03/17] ipmi: Add a KCS low-level interface minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 04/17] ipmi: Add a BT " minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 05/17] ipmi: Add a local BMC simulation minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 06/17] ipmi: Add an external connection simulation interface minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 07/17] ipmi: Add tests minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 08/17] ipmi: Add documentation minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 09/17] ipmi: Add migration capability to the IPMI device minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 10/17] ipmi: Add a firmware configuration repository minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 12/17] smbios: Add a function to directly add an entry minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 13/17] pc: Postpone SMBIOS table installation to post machine init minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 14/17] ipmi: Add SMBIOS table entry minyard
2015-04-26  8:36   ` Michael S. Tsirkin
2015-04-23 22:57 ` [Qemu-devel] [PATCH 15/17] acpi: Add a way for devices to add ACPI tables minyard
2015-04-23 22:57 ` [Qemu-devel] [PATCH 16/17] ipmi: Add ACPI table entries minyard
2015-04-26  8:36   ` Michael S. Tsirkin
2015-04-23 22:57 ` [Qemu-devel] [PATCH 17/17] bios: Add tests for the IPMI ACPI and SMBIOS entries minyard
2015-04-23 23:11 ` [Qemu-devel] [PATCH 00/17] Update to adding an IPMI device to qemu Eric Blake
2015-04-26 11:39   ` Andreas Färber
2015-04-26 16:52     ` Paolo Bonzini
2015-04-27 13:19     ` Corey Minyard
2015-04-24  9:38 ` Paolo Bonzini
2015-04-24 13:07   ` Corey Minyard

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=555109F6.9020108@acm.org \
    --to=minyard@acm.org \
    --cc=afaerber@suse.de \
    --cc=cminyard@mvista.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@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).