All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
To: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: guz.fnst@cn.fujitsu.com, imammedo@redhat.com,
	zhugh.fnst@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
	tangchen@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH 1/2] cpu/apic: drop icc bus/bridge/
Date: Wed, 18 Mar 2015 09:16:28 +0800	[thread overview]
Message-ID: <5508D1EC.1050204@cn.fujitsu.com> (raw)
In-Reply-To: <55080445.6020202@suse.de>


On 03/17/2015 06:39 PM, Andreas Färber wrote:
> Am 17.03.2015 um 10:08 schrieb Chen Fan:
>> ICC bus was invented only to provide hotplug capability to
>> CPU and APIC because at the time being hotplug was available only for
>> BUS attached devices.
>>
>> Now this patch is to drop ICC bus impl, and switch to bus-less
>> CPU+APIC hotplug, handling them in the same manner as pc-dimm.
>>
>> Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
>> ---
>>   hw/i386/pc.c                    | 21 +++++----------------
>>   hw/i386/pc_piix.c               |  9 +--------
>>   hw/i386/pc_q35.c                |  9 +--------
>>   hw/intc/apic.c                  |  6 +++---
>>   hw/intc/apic_common.c           | 24 +++++++++++++++++++-----
>>   include/hw/i386/apic_internal.h |  5 ++---
>>   include/hw/i386/pc.h            |  2 +-
>>   target-i386/cpu.c               | 15 ++-------------
>>   target-i386/cpu.h               |  2 +-
>>   9 files changed, 35 insertions(+), 58 deletions(-)
> This mini-series is lacking a cover letter and a change log.
> Please also find a better subject for this one: Luckily you are not just
> dropping things but rather implementing the new hotplug interface.
>
> Is this a resend from Zhu Guihua's series or did anything change?
> I think for Soft Freeze and Hard Freeze coming up today it's too late.
I picked up this two patches from Zhu Guihua's series separately and made
some changed to better adapt new interface.

>
> As you may have seen, I've posted a test case to facilitate testing of
> the various proposed code movements.
yes, I would use it to test my later version.

Thanks,
Chen

>
> Regards,
> Andreas
>

  reply	other threads:[~2015-03-18  1:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17  9:08 [Qemu-devel] [PATCH 1/2] cpu/apic: drop icc bus/bridge/ Chen Fan
2015-03-17  9:08 ` [Qemu-devel] [PATCH 2/2] icc_bus: remove icc related files Chen Fan
2015-03-17 10:39 ` [Qemu-devel] [PATCH 1/2] cpu/apic: drop icc bus/bridge/ Andreas Färber
2015-03-18  1:16   ` Chen Fan [this message]
2015-03-19  9:07   ` Chen Fan
2015-03-19 11:49     ` Andreas Färber
2015-03-17 16:29 ` Igor Mammedov
2015-03-19 10:08   ` Chen Fan
2015-03-19 10:28     ` 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=5508D1EC.1050204@cn.fujitsu.com \
    --to=chen.fan.fnst@cn.fujitsu.com \
    --cc=afaerber@suse.de \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=imammedo@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.