From: Alexander Graf <agraf@suse.de>
To: Fabien Chouteau <chouteau@adacore.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: Tristan Gingold <gingold@adacore.com>
Subject: Re: [Qemu-devel] [PATCH] [POWERPC] display cpu id dump state
Date: Thu, 26 Feb 2015 13:17:53 +0100 [thread overview]
Message-ID: <54EF0EF1.1010000@suse.de> (raw)
In-Reply-To: <1424857165-26277-1-git-send-email-chouteau@adacore.com>
On 25.02.15 10:39, Fabien Chouteau wrote:
> From: Tristan Gingold <gingold@adacore.com>
>
>
> Signed-off-by: Fabien Chouteau <chouteau@adacore.com>
Same nit here - please always provide a commit message stating your
rationale. I can guess (debugging SMP guests), but it's nicer when you
can look through the logs and there's no need to guess.
Alex
> ---
> target-ppc/translate.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/target-ppc/translate.c b/target-ppc/translate.c
> index 88c18e3..2a78e99 100644
> --- a/target-ppc/translate.c
> +++ b/target-ppc/translate.c
> @@ -11214,8 +11214,9 @@ void ppc_cpu_dump_state(CPUState *cs, FILE *f, fprintf_function cpu_fprintf,
> int i;
>
> cpu_fprintf(f, "NIP " TARGET_FMT_lx " LR " TARGET_FMT_lx " CTR "
> - TARGET_FMT_lx " XER " TARGET_FMT_lx "\n",
> - env->nip, env->lr, env->ctr, cpu_read_xer(env));
> + TARGET_FMT_lx " XER " TARGET_FMT_lx " CPU#%d\n",
> + env->nip, env->lr, env->ctr, cpu_read_xer(env),
> + cs->cpu_index);
> cpu_fprintf(f, "MSR " TARGET_FMT_lx " HID0 " TARGET_FMT_lx " HF "
> TARGET_FMT_lx " idx %d\n", env->msr, env->spr[SPR_HID0],
> env->hflags, env->mmu_idx);
>
next prev parent reply other threads:[~2015-02-26 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 9:39 [Qemu-devel] [PATCH] [POWERPC] display cpu id dump state Fabien Chouteau
2015-02-26 12:17 ` Alexander Graf [this message]
2015-02-26 12:18 ` Alexander Graf
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=54EF0EF1.1010000@suse.de \
--to=agraf@suse.de \
--cc=chouteau@adacore.com \
--cc=gingold@adacore.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).