qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Butsykin <pbutsykin@odin.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Denis V. Lunev" <den@openvz.org>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Pavel Butsykin <pbutsykin@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] monitor: remove target-specific code from monitor.c
Date: Fri, 28 Aug 2015 17:58:31 +0300	[thread overview]
Message-ID: <55E07717.50807@odin.com> (raw)
In-Reply-To: <CAFEAcA8Ujhs=g7g_kBCGJTF4BhKwn4Nx7WX3-LeSMLwoX0AHAg@mail.gmail.com>



On 28.08.2015 13:12, Peter Maydell wrote:
> On 28 August 2015 at 10:21, Pavel Butsykin <pbutsykin@odin.com> wrote:
>> Yes, this is a good way if we make the interface: const MonitorDef
>> *target_monitor_defs(void);
>> But we can't include the 'monitor/monitor-common.h' to
>> stubs/target-monitor-defs.c, because
>> there is a dependency with a target-specific headers( such as
>> cpu.h:CPUArchState, cpu-defs.h:target_long).
>> Make a copy of the struct MonitorDef not a good way because we can miss the
>> change of copied MonitorDef
>> in stubs/target-monitor-defs.c and this will result in an bug. Can this be
>> solved somehow else?
> That target_long is awkward. I suggest making the stub version
> just return NULL rather than a pointer to an empty list (you'll
> need to adjust the calling code slightly to handle the NULL
> return). Then the stub code only needs to be able to see the
> 'typedef struct MonitorDef MonitorDef' (which you can put in
> qemu-typedefs.h).
>
> -- PMM
Thank you for the suggestion, this seems a good way out.

  reply	other threads:[~2015-08-28 14:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 11:50 [Qemu-devel] [PATCH v2 for 2.5 0/3] Move target- and device specific code from monitor Denis V. Lunev
2015-08-12 11:50 ` [Qemu-devel] [PATCH 1/3] hmp-commands-info: move info_cmds content out of monitor.c Denis V. Lunev
2015-08-27 17:40   ` Peter Maydell
2015-08-12 11:50 ` [Qemu-devel] [PATCH 2/3] monitor: remove target-specific code from monitor.c Denis V. Lunev
2015-08-27 17:31   ` Peter Maydell
2015-08-27 17:37     ` Denis V. Lunev
2015-08-28  9:21     ` Pavel Butsykin
2015-08-28 10:12       ` Peter Maydell
2015-08-28 14:58         ` Pavel Butsykin [this message]
2015-08-12 11:50 ` [Qemu-devel] [PATCH 3/3] monitor: added generation of documentation for hmp-commands-info.hx Denis V. Lunev
2015-08-27 17:39   ` Peter Maydell
2015-08-28  7:00     ` Pavel Butsykin
2015-08-28  8:19       ` Peter Maydell
2015-08-28 14:53         ` Pavel Butsykin
2015-08-18 23:50 ` [Qemu-devel] [PATCH v2 for 2.5 0/3] Move target- and device specific code from monitor Denis V. Lunev
2015-08-25  9:54 ` Denis V. Lunev
2015-08-27 11:27   ` Denis V. Lunev
2015-08-27 12:13     ` Peter Maydell
2015-08-27 12:34       ` Denis V. Lunev
2015-08-28 11:25 ` Markus Armbruster
  -- strict thread matches above, loose matches on Subject: below --
2015-07-02 16:18 [Qemu-devel] (no subject) Denis V. Lunev
2015-07-02 16:18 ` [Qemu-devel] [PATCH 2/3] monitor: remove target-specific code from monitor.c Denis V. Lunev

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=55E07717.50807@odin.com \
    --to=pbutsykin@odin.com \
    --cc=den@openvz.org \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pbutsykin@virtuozzo.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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).