From: 赵小强 <zxq_yx_007@163.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] kvm/apic: use QOM style
Date: Tue, 05 Nov 2013 09:23:17 +0800 [thread overview]
Message-ID: <52784885.5050108@163.com> (raw)
In-Reply-To: <5277D7FF.2090100@suse.de>
于 11/05/2013 01:23 AM, Andreas Färber 写道:
> Hi,
>
> Am 04.11.2013 07:41, schrieb 赵小强:
>> 于 09/27/2013 01:30 PM, xiaoqiang zhao 写道:
>>> From: "xiaoqiang.zhao" <zxq_yx_007@163.com>
>>>
>>> Change apic and kvm/apic to use QOM interface.
>>>
>>> Includes:
>>> 1. APICCommonState now use QOM realizefn
>>> 2. Remove DO_UPCAST() for APICCommonState
>>> 3. Use type constant
>>> 4. Change DeviceState pointers from 'd' to 'dev', sounds better?
>>>
>>> Signed-off-by: xiaoqiang zhao <zxq_yx_007@163.com>
>>> ---
>>> hw/i386/kvm/apic.c | 40 ++++++++++++++++++----
>>> hw/intc/apic.c | 70
>>> +++++++++++++++++++++++++--------------
>>> hw/intc/apic_common.c | 70
>>> +++++++++++++++++++--------------------
>>> include/hw/i386/apic_internal.h | 1 -
>>> 4 files changed, 113 insertions(+), 68 deletions(-)
> [...]
>> ping.
>> patch link:
>> http://patchwork.ozlabs.org/patch/278481
>> http://patchwork.ozlabs.org/patch/278476
> Thanks for reminding. A couple of issues with these two patches:
>
> When sending more than one patch, please include a small cover letter.
> That gives a better overview and gives you a central place to ping or us
> to provide review comments covering both patches.
>
> The DO_UPCAST() is a good cleanup, please put it in a separate patch to
> decouple it from the rest.
>
> As for d vs. dev, I've usually only changed it for the init/realize
> functions I touched or when there was a new name conflict between
> generic and specific device. But I'm fine with all your d changes. Just
> please put them in a cleanup patch together with DO_UPCAST(), same for
> the register_types prefix, then the actual "dangerous" patch becomes
> smaller and thus easier to review for us. (Instead of 2 you'd have 4.)
>
> The main issue though is that Anthony has requested to change the
> pattern for overriding virtual methods: Can you please update the patch
> so that void (*init)(APICCommonState *dev); simply gets replaced by
> DeviceRealize realize;? I.e. drop the two new ...Class'es and
> parent_realize, leave the call logic as it is now and just update the
> function signature. Same for the ioapic.
>
> For the second patch, I'd appreciate a second reviewer for the static
> variable being refactored.
> Note that you can pull the DEVICE(s) -> dev conversion into a preceding
> cleanup patch by introducing a local DeviceState *dev = DEVICE(s).
> Also there's some minor whitespace issues in ioapic_common_realize()
> that we'll need to fix.
>
> Thanks in advance and sorry for the delay,
>
> Andreas
>
Thanks for your reply!
prev parent reply other threads:[~2013-11-05 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 5:30 [Qemu-devel] [PATCH 1/2] kvm/apic: use QOM style xiaoqiang zhao
2013-09-27 5:30 ` [Qemu-devel] [PATCH 2/2] ioapic " xiaoqiang zhao
2013-11-04 6:41 ` [Qemu-devel] [PATCH 1/2] kvm/apic: " 赵小强
2013-11-04 17:23 ` Andreas Färber
2013-11-05 1:23 ` 赵小强 [this message]
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=52784885.5050108@163.com \
--to=zxq_yx_007@163.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.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 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.