From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: "Alexander Graf" <agraf@suse.de>,
"Markus Armbruster" <armbru@redhat.com>,
"Luiz Capitulino" <lcapitulino@redhat.com>,
qemu-ppc@nongnu.org, "Andreas Färber" <afaerber@suse.de>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH qemu 2/2] target-ppc: Define get_monitor_def
Date: Thu, 6 Aug 2015 17:00:28 +1000 [thread overview]
Message-ID: <55C3060C.8010108@ozlabs.ru> (raw)
In-Reply-To: <55C2FF9F.3000607@redhat.com>
On 08/06/2015 04:33 PM, Thomas Huth wrote:
> On 06/08/15 07:25, Alexey Kardashevskiy wrote:
>> At the moment get_monitor_def() prints only registers from monitor_defs.
>> However there is a lot of BOOK3S SPRs which are not in the list and
>> cannot be printed.
>>
>> This makes use of the new get_monitor_def() callback and prints all
>> registered SPRs and fails on unregistered ones proving the user
>> information on what is actually supported in the running CPU.
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> ---
>> monitor.c | 215 +-------------------------------------------
>> target-ppc/cpu-qom.h | 2 +
>> target-ppc/translate.c | 72 +++++++++++++++
>> target-ppc/translate_init.c | 1 +
>> 4 files changed, 76 insertions(+), 214 deletions(-)
> ...
>> diff --git a/target-ppc/translate.c b/target-ppc/translate.c
>> index 84c5cea..f4acafb 100644
>> --- a/target-ppc/translate.c
>> +++ b/target-ppc/translate.c
>> @@ -11401,6 +11401,78 @@ void ppc_cpu_dump_statistics(CPUState *cs, FILE*f,
>> #endif
>> }
>>
>> +static int ppc_cpu_get_reg(target_ulong *regs, const char *numstr, int maxnum,
>> + uint64_t *pval)
>
> Don't you break the 32-bit QEMU (ppc-softmmu instead of ppc64-softmmu)
> here? Since pval is uint64_t but the registers are target_ulong = 32 bit ?
I cannot see how I break it - 64bit is enough for both, 32bit will just
have upper bits set to zero.
>
>> +{
>> + char *endptr = NULL;
>> + int regnum = strtoul(numstr, &endptr, 10);
>> +
>> + if ((endptr && *endptr) || (regnum >= maxnum)) {
>
> I'll never get used to your bracketism...
>
>> + return -EINVAL;
>> + }
>> + *pval = regs[regnum];
>> +
>> + return 0;
>> +}
>> +
>> +int ppc_cpu_get_monitor_def(CPUState *cs, const char *name, uint64_t *pval)
>> +{
>> + int i;
>> + PowerPCCPU *cpu = POWERPC_CPU(cs);
>> + CPUPPCState *env = &cpu->env;
>> +
>> +#define MONREG(s, f) \
>> + if ((strcasecmp((s), name) == 0)) { \
>
> Remove at least here the outermost round brackets?
Oh, leftovers...
>> + *pval = (f); \
>> + return 0; \
>> + }
>
> ... also defining a macro with parameters and code within a function
> looks somewhat strange to me. Maybe you could consider moving this in
> front of the function?
Why? It is very very local and not intended to be used anywhere else, why
to push people to look for their definitions somewhere else?
>> + MONREG("pc", env->nip)
>> + MONREG("nip", env->nip)
>> + MONREG("lr", env->lr)
>> + MONREG("ctr", env->ctr)
>> + MONREG("xer", env->xer)
>> + MONREG("decr", cpu_ppc_load_decr(env))
>> + MONREG("msr", env->msr)
>> + MONREG("tbu", cpu_ppc_load_tbu(env))
>> + MONREG("tbl", cpu_ppc_load_tbl(env))
>> +
>> + if (strcasecmp("ccr", name) == 0) {
>> + unsigned int u = 0;
>> +
>> + for (i = 0; i < 8; i++)
>> + u |= env->crf[i] << (32 - (4 * (i + 1)));
>> +
>> + return u;
>> + }
>> +
>> + /* General purpose registers */
>> + if (name[0] == 'r') {
>> + return ppc_cpu_get_reg(env->gpr, name + 1, ARRAY_SIZE(env->gpr), pval);
>> + }
>> +
>> + /* Floating point registers */
>> + if (name[0] == 'f') {
>> + return ppc_cpu_get_reg(env->fpr, name + 1, ARRAY_SIZE(env->fpr), pval);
>> + }
>> +
>> + /* Segment registers */
>> + if (strncmp(name, "sr", 2) == 0) {
>> + return ppc_cpu_get_reg(env->sr, name + 2, ARRAY_SIZE(env->sr), pval);
>> + }
>> +
>> + /* Special purpose registers */
>> + for (i = 0; i < ARRAY_SIZE(env->spr_cb); ++i) {
>> + ppc_spr_t *spr = &env->spr_cb[i];
>> +
>> + if (spr->name && (strcasecmp(name, spr->name) == 0)) {
>> + *pval = env->spr[i];
>> + return 0;
>> + }
>> + }
>> +
>> + return -EINVAL;
>> +}
>
> Since translate.c is very overcrowded already ... maybe you could put
> this code into a separate file instead? target-ppc/monitor.c ? Or maybe
> target-ppc/cpu.c ?
Well, I will do that as well (and move ppc_cpu_dump_state&co to this new
file) if the whole approach will be ack'ed.
--
Alexey
next prev parent reply other threads:[~2015-08-06 7:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 5:25 [Qemu-devel] [PATCH qemu 0/2] monitor/ppc: Print correct SPRs Alexey Kardashevskiy
2015-08-06 5:25 ` [Qemu-devel] [PATCH qemu 1/2] monitor: Add CPU class callback to read registers for monitor Alexey Kardashevskiy
2015-08-12 1:12 ` David Gibson
2015-08-06 5:25 ` [Qemu-devel] [PATCH qemu 2/2] target-ppc: Define get_monitor_def Alexey Kardashevskiy
2015-08-06 6:33 ` Thomas Huth
2015-08-06 7:00 ` Alexey Kardashevskiy [this message]
2015-08-06 7:07 ` Thomas Huth
2015-08-12 1:21 ` David Gibson
2015-08-13 15:52 ` [Qemu-devel] [PATCH qemu v2] " Alexey Kardashevskiy
2015-08-13 22:39 ` David Gibson
2015-08-14 3:34 ` [Qemu-devel] [PATCH qemu v3] " Alexey Kardashevskiy
2015-09-07 1:26 ` Alexey Kardashevskiy
2015-09-23 3:40 ` David Gibson
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=55C3060C.8010108@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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).