From: Igor Mammedov <imammedo@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"aliguori@us.ibm.com" <aliguori@us.ibm.com>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"mdroth@linux.vnet.ibm.com" <mdroth@linux.vnet.ibm.com>,
"sw@weilnetz.de" <sw@weilnetz.de>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"agraf@suse.de" <agraf@suse.de>,
"blauwirbel@gmail.com" <blauwirbel@gmail.com>,
"jcmvbkbc@gmail.com" <jcmvbkbc@gmail.com>,
"avi@redhat.com" <avi@redhat.com>,
"afaerber@suse.de" <afaerber@suse.de>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 0/4 v2] target-i386: move tcg intialization inside CPU object
Date: Tue, 03 Jul 2012 11:56:46 +0200 [thread overview]
Message-ID: <4FF2C1DE.1030109@redhat.com> (raw)
In-Reply-To: <4FEC4C43.3080006@siemens.com>
On 06/28/2012 02:21 PM, Jan Kiszka wrote:
> On 2012-06-25 15:55, Igor Mammedov wrote:
>> 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(-)
>>
>
> Looks good to me.
Thanks for reviews guys.
Jan,
I'm still learning about review process rules. Does usually or in your case "Looks good to me" implies Reviewed-By:... ?
And do I have to send pull request or ask somebody (whom?) to take patches in?
> Jan
>
--
-----
Igor
next parent reply other threads:[~2012-07-03 9:57 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 ` Igor Mammedov [this message]
2012-07-10 15:56 ` [Qemu-devel] [PATCH 0/4 v2] target-i386: move tcg intialization inside CPU object 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
[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=4FF2C1DE.1030109@redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jcmvbkbc@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mtosatti@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sw@weilnetz.de \
/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).