From: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: ehabkost@redhat.com, qemu-devel@nongnu.org,
izumi.taku@jp.fujitsu.com, chen.fan.fnst@cn.fujitsu.com,
pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v9 0/4] remove icc bus/bridge
Date: Mon, 20 Jul 2015 09:00:06 +0800 [thread overview]
Message-ID: <55AC4816.50706@cn.fujitsu.com> (raw)
In-Reply-To: <20150716115237.6415d01e@nial.brq.redhat.com>
On 07/16/2015 05:52 PM, Igor Mammedov wrote:
> On Thu, 16 Jul 2015 10:45:41 +0800
> Zhu Guihua <zhugh.fnst@cn.fujitsu.com> wrote:
>
>> ping...
> I'll look at it once 2.4 is released.
Got it, thanks.
By the way, do you know what state of qemu socket topology ?
Regards,
Zhu
>
>> On 07/03/2015 05:38 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.
>>>
>>> v9:
>>> -use a callback to correct reset sequence for x86
>>> -update apic mmio mapping
>>>
>>> v8:
>>> -add a wrapper to specify reset order
>>>
>>> v7:
>>> -update to register reset handler for main_system_bus when created
>>> -register reset handler for apic after all devices are initialized
>>>
>>> Chen Fan (2):
>>> apic: map APIC's MMIO region at each CPU's address space
>>> cpu/apic: drop icc bus/bridge
>>>
>>> Zhu Guihua (2):
>>> 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 | 43 +++++++-------
>>> 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 | 30 +++++++---
>>> 12 files changed, 52 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-07-20 1:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 9:38 [Qemu-devel] [PATCH v9 0/4] remove icc bus/bridge Zhu Guihua
2015-07-03 9:38 ` [Qemu-devel] [PATCH v9 1/4] apic: map APIC's MMIO region at each CPU's address space Zhu Guihua
2015-07-03 9:38 ` [Qemu-devel] [PATCH v9 2/4] x86: use new method to correct reset sequence Zhu Guihua
2015-07-03 9:38 ` [Qemu-devel] [PATCH v9 3/4] cpu/apic: drop icc bus/bridge Zhu Guihua
2015-07-03 9:38 ` [Qemu-devel] [PATCH v9 4/4] icc_bus: drop the unused files Zhu Guihua
2015-07-16 2:45 ` [Qemu-devel] [PATCH v9 0/4] remove icc bus/bridge Zhu Guihua
2015-07-16 9:52 ` Igor Mammedov
2015-07-20 1:00 ` Zhu Guihua [this message]
2015-07-20 7:07 ` Igor Mammedov
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=55AC4816.50706@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).