From: Paolo Bonzini <pbonzini@redhat.com>
To: Liu Ping Fan <qemulist@gmail.com>
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, "Anthony Liguori" <anthony@codemonkey.ws>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 4/5] qom-cpu: during cpu reset, it will reset its child
Date: Tue, 10 Jul 2012 10:41:59 +0200 [thread overview]
Message-ID: <4FFBEAD7.6060705@redhat.com> (raw)
In-Reply-To: <1341900967-4344-5-git-send-email-qemulist@gmail.com>
Il 10/07/2012 08:16, Liu Ping Fan ha scritto:
> This will give the embeded logic module, such as apic has the
> opportunity to reset.
>
> Signed-off-by: Liu Ping Fan <pingfank@linux.vnet.ibm.com>
> ---
> qom/cpu.c | 16 ++++++++++++++++
> 1 files changed, 16 insertions(+), 0 deletions(-)
>
> diff --git a/qom/cpu.c b/qom/cpu.c
> index 5b36046..6aea8e6 100644
> --- a/qom/cpu.c
> +++ b/qom/cpu.c
> @@ -20,10 +20,26 @@
>
> #include "qemu/cpu.h"
> #include "qemu-common.h"
> +#include "hw/qdev.h"
> +
> +static int cpu_reset_kid(Object *child, void *opaque)
> +{
> + if (object_is_type_str(child, TYPE_DEVICE)) {
> + device_reset(DEVICE(child));
> + } else if (object_is_type_str(child, TYPE_BUS)) {
> + bus_reset(BUS(child));
> + } else {
> + printf("cpu's child must be DEVICE or BUS");
> + abort();
> + }
> + return 0;
> +}
>
> void cpu_reset(CPUState *cpu)
> {
> CPUClass *klass = CPU_GET_CLASS(cpu);
> + Object *obj = OBJECT(cpu);
> + object_child_foreach(obj, cpu_reset_kid, NULL);
Ok, now I see what you want to do. Next time, please add meaningful
commit messages to all patches in the series, even those that only add
infrastructure.
It really looks like time is ripe to make CPUs children of Device, so
you can just use qdev_reset_all to reset the CPU.
Paolo
> if (klass->reset != NULL) {
> (*klass->reset)(cpu);
>
next prev parent reply other threads:[~2012-07-10 8:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 6:16 [Qemu-devel] make apic hot-plugable Liu Ping Fan
2012-07-10 6:16 ` [Qemu-devel] [PATCH 1/5] qdev: introduce qdev_create_kid(Object *parent, const char *type) Liu Ping Fan
2012-07-10 8:12 ` Andreas Färber
2012-07-10 8:45 ` Paolo Bonzini
2012-07-11 1:17 ` liu ping fan
2012-07-11 7:01 ` Paolo Bonzini
2012-07-10 6:16 ` [Qemu-devel] [PATCH 2/5] qom: introduce object_is_type_str(), so we can judge its type Liu Ping Fan
2012-07-10 8:39 ` Paolo Bonzini
2012-07-11 1:17 ` liu ping fan
2012-07-10 6:16 ` [Qemu-devel] [PATCH 3/5] qdev: export the bus reset interface Liu Ping Fan
2012-07-10 8:40 ` Paolo Bonzini
2012-07-10 6:16 ` [Qemu-devel] [PATCH 4/5] qom-cpu: during cpu reset, it will reset its child Liu Ping Fan
2012-07-10 8:41 ` Paolo Bonzini [this message]
2012-07-10 10:12 ` Andreas Färber
2012-07-11 1:17 ` liu ping fan
2012-07-11 12:37 ` Igor Mammedov
2012-07-11 1:17 ` liu ping fan
2012-07-11 7:02 ` Paolo Bonzini
2012-07-10 6:16 ` [Qemu-devel] [PATCH 5/5] apic: create apic as a child of cpu, not system_bus any longer Liu Ping Fan
2012-07-10 8:45 ` Paolo Bonzini
2012-07-10 10:41 ` Andreas Färber
2012-07-11 8:41 ` Igor Mammedov
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=4FFBEAD7.6060705@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@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).