From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: zhugh.fnst@cn.fujitsu.com, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, tangchen@cn.fujitsu.com,
Gu Zheng <guz.fnst@cn.fujitsu.com>,
isimatu.yasuaki@jp.fujitsu.com,
Igor Mammedov <imammedo@redhat.com>,
chen.fan.fnst@cn.fujitsu.com, Paolo Bonzini <pbonzini@redhat.com>,
anshul.makkar@profitbricks.com
Subject: Re: [Qemu-devel] [PATCH 1/1] target-i386: Remove icc_bridge parameter from cpu_x86_create()
Date: Tue, 10 Mar 2015 14:33:17 +0100 [thread overview]
Message-ID: <54FEF29D.9070405@suse.de> (raw)
In-Reply-To: <20150310133057.GB3513@thinpad.lan.raisama.net>
Am 10.03.2015 um 14:30 schrieb Eduardo Habkost:
> On Tue, Mar 10, 2015 at 02:22:01PM +0100, Andreas Färber wrote:
>> Am 05.03.2015 um 18:26 schrieb Eduardo Habkost:
>>> Instead of passing icc_bridge from the PC initialization code to
>>> cpu_x86_create(), make the PC initialization code attach the CPU to
>>> icc_bridge.
>>>
>>> The only difference here is that icc_bridge attachment will now be done
>>> after x86_cpu_parse_featurestr() is called. But this shouldn't make any
>>> difference, as property setters shouldn't depend on icc_bridge.
>>>
>>> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
>>> ---
>>> hw/i386/pc.c | 6 +++++-
>>> target-i386/cpu.c | 14 ++------------
>>> target-i386/cpu.h | 3 +--
>>> 3 files changed, 8 insertions(+), 15 deletions(-)
>>>
>>> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
>>> index ed54d93..66b9fa6 100644
>>> --- a/hw/i386/pc.c
>>> +++ b/hw/i386/pc.c
>>> @@ -995,12 +995,16 @@ static X86CPU *pc_new_cpu(const char *cpu_model, int64_t apic_id,
>>> X86CPU *cpu;
>>> Error *local_err = NULL;
>>>
>>> - cpu = cpu_x86_create(cpu_model, icc_bridge, &local_err);
>>> + cpu = cpu_x86_create(cpu_model, &local_err);
>>> if (local_err != NULL) {
>>> error_propagate(errp, local_err);
>>> return NULL;
>>> }
>>>
>>> + assert(icc_bridge);
>>
>> On second thoughts, why are you asserting here rather than setting errp?
>> Just add an out: below and goto out, like I did.
>>
>> On startup it doesn't matter much, but for hot-add asserting would not
>> be so nice.
>
> Because not having icc_bus passed as argument would be a coding error.
>
> Also, I have no idea what kind of things would break if we destroy a CPU
> after cpu_exec_init() was already called in instance_init.
Then do it before cpu_x86_create()! :)
Also, every memory allocation failure can result in an assertion (which
is why I'm trying to cut down on their number).
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-03-10 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 17:26 [Qemu-devel] [PATCH 0/1] target-i386: Move icc_bridge code to PC Eduardo Habkost
2015-03-05 17:26 ` [Qemu-devel] [PATCH 1/1] target-i386: Remove icc_bridge parameter from cpu_x86_create() Eduardo Habkost
2015-03-10 11:50 ` Andreas Färber
2015-03-10 12:42 ` Eduardo Habkost
2015-03-10 12:51 ` Andreas Färber
2015-03-10 13:24 ` Eduardo Habkost
2015-03-10 13:30 ` Andreas Färber
2015-03-10 13:48 ` Eduardo Habkost
2015-03-10 13:22 ` Andreas Färber
2015-03-10 13:30 ` Eduardo Habkost
2015-03-10 13:33 ` Andreas Färber [this message]
2015-03-10 14:49 ` 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=54FEF29D.9070405@suse.de \
--to=afaerber@suse.de \
--cc=anshul.makkar@profitbricks.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=ehabkost@redhat.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 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.