From: "Andreas Färber" <afaerber@suse.de>
To: Igor Mammedov <imammedo@redhat.com>,
aliguori@us.ibm.com, Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4 v2] target-i386: move tcg intialization inside CPU object
Date: Thu, 09 Aug 2012 17:17:01 +0200 [thread overview]
Message-ID: <5023D46D.4040807@suse.de> (raw)
In-Reply-To: <1777008592.7127564.1344425336779.JavaMail.root@redhat.com>
Am 08.08.2012 13:28, schrieb Igor Mammedov:
> ping
FWIW it looks to me as if Jan's previous review comments regarding
debug_excp_helper have been addressed. So if someone could take a look
at patch 3/4 and ack that we don't need chaining of handlers, this
should be good to go for 1.2.
Andreas
>
> ----- Original Message -----
>> From: "Igor Mammedov" <imammedo@redhat.com>
>> To: qemu-devel@nongnu.org
>> Cc: "peter maydell" <peter.maydell@linaro.org>, aliguori@us.ibm.com, ehabkost@redhat.com, sw@weilnetz.de,
>> mtosatti@redhat.com, agraf@suse.de, mdroth@linux.vnet.ibm.com, blauwirbel@gmail.com, jcmvbkbc@gmail.com,
>> avi@redhat.com, "jan kiszka" <jan.kiszka@siemens.com>, afaerber@suse.de, rth@twiddle.net
>> Sent: Monday, June 25, 2012 3:55:03 PM
>> Subject: [Qemu-devel] [PATCH 0/4 v2] target-i386: move tcg intialization inside CPU object
>>
>> v2:
>> - drop usage of prev_debug_excp_handler consistently in all users
>> - split from reset patches to avoid confusion of inter-dependency
>>
>> Compile & Run tested:
>> target-i386: tcg and kvm mode
>> i386-linux-user: running of /bin/ls
>> Compile tested:
>> xtensa-softmmu && xtensaeb-softmmu
>>
>> git tree for testing:
>> https://github.com/imammedo/qemu/tree/x86cpu_qom_tcg_v2
>>
>>
>> Igor Mammedov (4):
>> target-i386: drop usage of prev_debug_excp_handler
>> target-xtensa: drop usage of prev_debug_excp_handler
>> cleanup cpu_set_debug_excp_handler
>> target-i386: move tcg initialization into x86_cpu_initfn()
>>
>> cpu-exec.c | 5 +----
>> exec-all.h | 2 +-
>> target-i386/cpu.c | 10 ++++++++++
>> target-i386/cpu.h | 1 +
>> target-i386/helper.c | 16 +---------------
>> target-xtensa/helper.c | 8 +-------
>> 6 files changed, 15 insertions(+), 27 deletions(-)
>>
>> --
>> 1.7.10.2
>>
>>
>>
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-08-09 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1340632507-29692-1-git-send-email-imammedo@redhat.com>
[not found] ` <4FEC4C43.3080006@siemens.com>
2012-07-03 9:56 ` [Qemu-devel] [PATCH 0/4 v2] target-i386: move tcg intialization inside CPU object Igor Mammedov
2012-07-10 15:56 ` Igor Mammedov
2012-07-23 7:46 ` Igor Mammedov
2012-08-09 19:59 ` Blue Swirl
2012-08-02 11:55 ` Igor Mammedov
2012-08-08 11:28 ` Igor Mammedov
2012-08-09 15:17 ` Andreas Färber [this message]
[not found] ` <1340632507-29692-2-git-send-email-imammedo@redhat.com>
2012-08-09 15:15 ` [Qemu-devel] [PATCH 1/4] target-i386: drop usage of prev_debug_excp_handler Andreas Färber
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=5023D46D.4040807@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=imammedo@redhat.com \
--cc=jan.kiszka@siemens.com \
--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).