From: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org, imammedo@redhat.com, afaerber@suse.de,
pbonzini@redhat.com, ehabkost@redhat.com
Cc: chen.fan.fnst@cn.fujitsu.com, izumi.taku@jp.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH v12 0/5] remove icc bus/bridge
Date: Wed, 30 Sep 2015 14:35:28 +0800 [thread overview]
Message-ID: <560B82B0.7040506@cn.fujitsu.com> (raw)
In-Reply-To: <cover.1442380656.git.zhugh.fnst@cn.fujitsu.com>
Hi Eduardo,
Can you help merge this patch series to your x86 tree?
Thanks,
Zhu
On 09/16/2015 05:19 PM, Zhu Guihua wrote:
> ICC Bus was used for providing a hotpluggable bus for APIC and CPU, but now we
> use HotplugHandler to make hotplug. So ICC Bus is unnecessary.
>
> This code has passed the new pc-cpu-test.
> And I have tested with kvm along with kernel_irqchip=on/off, it works fine.
>
> This patch series is based on the latest master.
>
> v12:
> -move APIC MMIO mapping into x86_cpu_apic_realize()
> -change commit message in PATCH 4
>
> v11:
> -improve commit messages
> -split per CPU AS change into a separate patch
>
> v10:
> -improve commit messages in patch 1 and 2
> -make the check of cpu->cpu_as_root simplier
>
> v9:
> -use a callback to correct reset sequence for x86
> -update apic mmio mapping
>
> Chen Fan (2):
> apic: move APIC's MMIO region mapping into APIC
> cpu/apic: drop icc bus/bridge
>
> Zhu Guihua (3):
> apic: use per CPU AS to map APIC MMIO for TCG
> x86: use new method to correct reset sequence
> icc_bus: drop the unused files
>
> default-configs/i386-softmmu.mak | 1 -
> default-configs/x86_64-softmmu.mak | 1 -
> hw/cpu/Makefile.objs | 1 -
> hw/cpu/icc_bus.c | 118 -------------------------------------
> hw/i386/pc.c | 46 ++++++++-------
> hw/i386/pc_piix.c | 9 +--
> hw/i386/pc_q35.c | 9 +--
> hw/intc/apic_common.c | 11 +---
> include/hw/cpu/icc_bus.h | 82 --------------------------
> include/hw/i386/apic_internal.h | 7 ++-
> include/hw/i386/pc.h | 2 +-
> target-i386/cpu.c | 33 ++++++++---
> 12 files changed, 58 insertions(+), 262 deletions(-)
> delete mode 100644 hw/cpu/icc_bus.c
> delete mode 100644 include/hw/cpu/icc_bus.h
>
next prev parent reply other threads:[~2015-09-30 6:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 9:19 [Qemu-devel] [PATCH v12 0/5] remove icc bus/bridge Zhu Guihua
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 1/5] apic: move APIC's MMIO region mapping into APIC Zhu Guihua
2015-09-22 12:28 ` Igor Mammedov
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 2/5] apic: use per CPU AS to map APIC MMIO for TCG Zhu Guihua
2015-09-22 12:29 ` Igor Mammedov
2015-10-02 18:24 ` Eduardo Habkost
2015-10-02 19:21 ` Eduardo Habkost
2015-10-09 9:00 ` Zhu Guihua
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 3/5] x86: use new method to correct reset sequence Zhu Guihua
2015-09-22 12:29 ` Igor Mammedov
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 4/5] cpu/apic: drop icc bus/bridge Zhu Guihua
2015-09-22 12:29 ` Igor Mammedov
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 5/5] icc_bus: drop the unused files Zhu Guihua
2015-09-22 12:30 ` Igor Mammedov
2015-09-30 6:35 ` Zhu Guihua [this message]
2015-10-02 17:58 ` [Qemu-devel] [PATCH v12 0/5] remove icc bus/bridge 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=560B82B0.7040506@cn.fujitsu.com \
--to=zhugh.fnst@cn.fujitsu.com \
--cc=afaerber@suse.de \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=pbonzini@redhat.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).