qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Peter Crosthwaite <crosthwaitepeter@gmail.com>,
	qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, edgari@xilinx.com,
	claudio.fontana@huawei.com, edgar.iglesias@gmail.com
Subject: Re: [Qemu-devel] [PATCH v2 2/7] disas: QOMify target specific setup
Date: Mon, 11 May 2015 08:50:45 -0700	[thread overview]
Message-ID: <5550CFD5.7070501@twiddle.net> (raw)
In-Reply-To: <5550C0BA.9000700@redhat.com>

On 05/11/2015 07:46 AM, Paolo Bonzini wrote:
> 
> 
> On 09/05/2015 22:11, Peter Crosthwaite wrote:
>> @@ -198,6 +199,8 @@ static int print_insn_od_target(bfd_vma pc, disassemble_info *info)
>>  void target_disas(FILE *out, CPUArchState *env, target_ulong code,
>>                    target_ulong size, int flags)
>>  {
>> +    CPUState *cpu = ENV_GET_CPU(env);
>> +    CPUClass *cc = CPU_GET_CLASS(cpu);
>>      target_ulong pc;
>>      int count;
>>      CPUDebug s;
>> @@ -215,6 +218,11 @@ void target_disas(FILE *out, CPUArchState *env, target_ulong code,
>>  #else
>>      s.info.endian = BFD_ENDIAN_LITTLE;
>>  #endif
>> +
>> +    if (cc->disas_set_info) {
>> +        cc->disas_set_info(cpu, &s.info);
>> +    }
>> +
>>  #if defined(TARGET_I386)
> 
> Perhaps pass down the flags too?

The hook is allowing us to ditch the flags.  See 4/7 and 7/7 for arm and cris
portions that do exactly that.


r~

  reply	other threads:[~2015-05-11 15:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 20:11 [Qemu-devel] [PATCH v2 0/7] Unify and QOMify (target|monitor)_disas Peter Crosthwaite
2015-05-09 20:11 ` [Qemu-devel] [PATCH v2 1/7] disas: Add print_insn to disassemble info Peter Crosthwaite
2015-05-11 15:51   ` Richard Henderson
2015-05-09 20:11 ` [Qemu-devel] [PATCH v2 2/7] disas: QOMify target specific setup Peter Crosthwaite
2015-05-11 14:46   ` Paolo Bonzini
2015-05-11 15:50     ` Richard Henderson [this message]
2015-05-11 15:51   ` Richard Henderson
2015-05-09 20:11 ` [Qemu-devel] [PATCH v2 3/7] disas: arm-a64: Make printfer and stream variable Peter Crosthwaite
2015-05-11 15:57   ` Richard Henderson
2015-05-24 21:28     ` Peter Crosthwaite
2015-05-09 20:11 ` [Qemu-devel] [PATCH v2 4/7] disas: arm: QOMify target specific disas setup Peter Crosthwaite
2015-05-18 16:31   ` Peter Maydell
2015-05-24 21:42     ` Peter Crosthwaite
2015-05-09 20:11 ` [Qemu-devel] [PATCH v2 5/7] disas: microblaze: " Peter Crosthwaite
2015-05-09 20:11 ` [Qemu-devel] [PATCH v2 6/7] disas: cris: Fix 0 buffer length case Peter Crosthwaite
2015-05-09 20:11 ` [Qemu-devel] [PATCH v2 7/7] disas: cris: QOMify target specific disas setup Peter Crosthwaite
2015-05-15  4:52 ` [Qemu-devel] [PATCH v2 0/7] Unify and QOMify (target|monitor)_disas Peter Crosthwaite
2015-05-15 13:33   ` Richard Henderson
2015-05-15 17:02     ` Peter Crosthwaite
2015-05-15 21:01     ` Peter Crosthwaite
2015-05-15 23:13       ` Peter Maydell

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=5550CFD5.7070501@twiddle.net \
    --to=rth@twiddle.net \
    --cc=claudio.fontana@huawei.com \
    --cc=crosthwaitepeter@gmail.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=edgari@xilinx.com \
    --cc=pbonzini@redhat.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).