From: Paolo Bonzini <pbonzini@redhat.com>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
aliguori@us.ibm.com, afaerber@suse.de, stefanha@gmail.com
Subject: Re: [Qemu-devel] [PATCH][RFC v2 3/7] vl: create power chip device
Date: Fri, 05 Apr 2013 13:48:58 +0200 [thread overview]
Message-ID: <515EBA2A.1090005@redhat.com> (raw)
In-Reply-To: <1365136091-26148-4-git-send-email-lig.fnst@cn.fujitsu.com>
Il 05/04/2013 06:28, liguang ha scritto:
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
> ---
> vl.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/vl.c b/vl.c
> index aeed7f4..a14549e 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -171,6 +171,8 @@ int main(int argc, char **argv)
> #include "ui/qemu-spice.h"
> #include "qapi/string-input-visitor.h"
>
> +#include "hw/power.h"
> +
> //#define DEBUG_NET
> //#define DEBUG_SLIRP
>
> @@ -4295,6 +4297,8 @@ int main(int argc, char **argv, char **envp)
>
> qdev_machine_init();
>
> + qdev_init_nofail(qdev_create(NULL, TYPE_POWER_CHIP));
> +
You cannot just add a random device to the machine.
Perhaps what you want to do is define a QOM interface that some device
in the machine will implement.
But right now this all seems very nebulous. Honestly, I read the
patches and I have no idea _why_ you are doing this.
Paolo
> QEMUMachineInitArgs args = { .ram_size = ram_size,
> .boot_device = (boot_devices[0] == '\0') ?
> machine->boot_order :
>
next prev parent reply other threads:[~2013-04-05 11:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 4:28 [Qemu-devel] [PATCH][RFC v2 0/7] implement power chip liguang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 1/7] hw/irq: move struct IRQState to irq.h liguang
2013-04-05 8:34 ` Peter Maydell
2013-04-05 8:39 ` li guang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 2/7] hw/power: add main power chip implementation liguang
2013-04-05 8:35 ` Peter Maydell
2013-04-05 8:45 ` li guang
2013-04-05 9:23 ` Peter Maydell
2013-04-08 0:32 ` li guang
2013-04-08 9:21 ` Peter Maydell
2013-04-09 8:14 ` li guang
2013-04-09 8:29 ` Paolo Bonzini
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 3/7] vl: create power chip device liguang
2013-04-05 11:48 ` Paolo Bonzini [this message]
2013-04-08 0:18 ` li guang
2013-04-08 9:53 ` Paolo Bonzini
2013-04-09 7:34 ` li guang
2013-04-09 7:43 ` Paolo Bonzini
2013-04-09 8:26 ` li guang
2013-04-09 11:06 ` Paolo Bonzini
2013-04-10 0:09 ` li guang
2013-04-10 9:40 ` Paolo Bonzini
2013-04-10 12:09 ` Andreas Färber
2013-04-10 13:41 ` guang li
2013-04-10 13:52 ` Paolo Bonzini
2013-04-11 1:30 ` li guang
2013-04-16 20:45 ` Anthony Liguori
2013-04-17 0:07 ` li guang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 4/7] sysemu: remove PowerReason in sysemu.h liguang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 5/7] qdev: add power_signal_in for DeviceState liguang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 6/7] ich9: refactor wakeup/reset function liguang
2013-04-05 4:28 ` [Qemu-devel] [PATCH][RFC v2 7/7] vl: run power_management liguang
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=515EBA2A.1090005@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).