From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: zhugh.fnst@cn.fujitsu.com, "Michael S. Tsirkin" <mst@redhat.com>,
tangchen@cn.fujitsu.com, chen.fan.fnst@cn.fujitsu.com,
isimatu.yasuaki@jp.fujitsu.com,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Gu Zheng" <guz.fnst@cn.fujitsu.com>,
"Igor Mammedov" <imammedo@redhat.com>,
anshul.makkar@profitbricks.com,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH v2 0/1] target-i386: Move icc_bridge code to PC
Date: Tue, 10 Mar 2015 18:57:34 -0300 [thread overview]
Message-ID: <1426024655-17561-1-git-send-email-ehabkost@redhat.com> (raw)
This removes yet another chunk of PC-specific code from target-i386/cpu.c and
moves it to PC code.
WIth this we get closer to being able to change target-i386 to use
cpu_generic_init().
This series is based on my x86 tree, located at:
https://github.com/ehabkost/qemu.git x86
Changes v1 -> v2:
* Keep existing check for NULL icc_bridge and error reporting, instead
of assing assert(icc_bridge)
Eduardo Habkost (1):
target-i386: Remove icc_bridge parameter from cpu_x86_create()
hw/i386/pc.c | 13 +++++++++++--
target-i386/cpu.c | 14 ++------------
target-i386/cpu.h | 3 +--
3 files changed, 14 insertions(+), 16 deletions(-)
--
2.1.0
next reply other threads:[~2015-03-10 21:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 21:57 Eduardo Habkost [this message]
2015-03-10 21:57 ` [Qemu-devel] [PATCH v2 1/1] target-i386: Remove icc_bridge parameter from cpu_x86_create() Eduardo Habkost
2015-03-10 22:43 ` Andreas Färber
2015-03-11 11:11 ` Eduardo Habkost
2015-03-11 11:59 ` Andreas Färber
2015-03-11 13:20 ` Eduardo Habkost
2015-03-11 13:36 ` Igor Mammedov
2015-03-11 13:49 ` Eduardo Habkost
2015-03-11 14:34 ` Igor Mammedov
2015-03-17 16:46 ` [Qemu-devel] [PATCH for-next] pc: Ensure non-zero CPU ref count after attaching to ICC bus Andreas Färber
2015-03-17 17:04 ` Eduardo Habkost
2015-03-17 17:09 ` Andreas Färber
2015-04-27 19:03 ` Michael S. Tsirkin
2015-04-27 19:27 ` Eduardo Habkost
2015-04-27 19:35 ` Eduardo Habkost
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=1426024655-17561-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=anshul.makkar@profitbricks.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tangchen@cn.fujitsu.com \
--cc=zhugh.fnst@cn.fujitsu.com \
/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).