From: Paolo Bonzini <bonzini@gnu.org>
To: David Gibson <david@gibson.dropbear.id.au>,
Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH qemu v4] monitor/target-ppc: Define target_get_monitor_def
Date: Wed, 11 Nov 2015 11:21:39 +0100 [thread overview]
Message-ID: <564316B3.7050700@gnu.org> (raw)
In-Reply-To: <20151111022728.GF5852@voom.redhat.com>
On 11/11/2015 03:27, David Gibson wrote:
> Meaning one which adds the hook to the monitor, and another which
> implements it for ppc? Maybe.
>
> I'd like to take this, but I'm not sure whether it's reasonable for
> the small generic monitor change to go through the ppc tree. Peter,
> Paolo, opinion?
I'm not a monitor maintainer, but I think it's okay since there is
none. :)
We probably should replace target_monitor_defs() with an implementation
of target_get_monitor_def on all targets. It can just pass a MonitorDef
array to a common function, i.e.
int lookup_monitor_def(MonitorDef *def, void *base, const char *name, uint64_t *pval)
static int target_get_monitor_def(CPUState *cs, const char *name, uint64_t *pval)
{
return lookup_monitor_def(monitor_defs, cs->env_ptr, name, pval);
}
I don't want you to do it now, but we should add it to the wiki
BiteSizedTasks so we don't forget.
Paolo
prev parent reply other threads:[~2015-11-11 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 6:16 [Qemu-devel] [PATCH qemu v4] monitor/target-ppc: Define target_get_monitor_def Alexey Kardashevskiy
2015-10-22 7:31 ` Alexey Kardashevskiy
2015-10-22 9:20 ` David Gibson
2015-10-23 22:22 ` Benjamin Herrenschmidt
2015-11-11 2:27 ` David Gibson
2015-11-11 10:21 ` Paolo Bonzini [this message]
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=564316B3.7050700@gnu.org \
--to=bonzini@gnu.org \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).