From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: marcel@redhat.com, pbonzini@redhat.com,
Zhu Guihua <zhugh.fnst@cn.fujitsu.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RESEND PATCH v3] i386: keep cpu_model field in MachineState uptodate
Date: Mon, 19 Oct 2015 18:47:50 +0200 [thread overview]
Message-ID: <56251EB6.5000105@suse.de> (raw)
In-Reply-To: <20151019154715.GD4914@thinpad.lan.raisama.net>
Am 19.10.2015 um 17:47 schrieb Eduardo Habkost:
> On Sun, Oct 18, 2015 at 06:22:40PM +0200, Andreas Färber wrote:
>> Am 18.10.2015 um 14:20 schrieb Michael S. Tsirkin:
>>> On Sun, Oct 18, 2015 at 02:18:31PM +0300, Marcel Apfelbaum wrote:
>>>> On 10/15/2015 06:12 AM, Zhu Guihua wrote:
> [...]
>>>>> - cpu = pc_new_cpu(current_cpu_model, apic_id, &local_err);
>>>>> + cpu = pc_new_cpu(machine->cpu_model, apic_id, &local_err);t
>>>>
>>>> Hi,
>>>>
>>>> I am not going to "stop" this patch and I do agree with what is trying to do.
>>>> What I still don't get is if we are "allowed" to directly access QOM object's private
>>>> fields outside the implementation C file.
>>>>
>>>> This is why we have some wrappers in include/hw/boards.h when we access machine's fields.
>>>>
>>>> Just wanted to raise the question, other than that (for what is worth):
>>>> Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>
>>>
>>> Andreas, could you ack/nack this patch pls?
>>
>> I won't nack it, as putting it into the QOM state now is a good idea.
>> But I would rather put this into PCMachineState, as current_cpu_model
>> was PC-only and I'd prefer not to encourage more uses of the old API.
>
> I don't undersand what you suggest. The patch doesn't add any new state,
> it is just updating the existing MachineState::cpu_model field (just
> like it is already done by multiple arm, mips, ppc, and tricore
> machines).
Looking at the full patch now, you are right. It is not adding a new
field but merely setting it.
Acked-by: Andreas Färber <afaerber@suse.de>
Sorry for the confusion,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2015-10-19 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 3:12 [Qemu-devel] [RESEND PATCH v3] i386: keep cpu_model field in MachineState uptodate Zhu Guihua
2015-10-16 15:06 ` Eduardo Habkost
2015-10-18 11:18 ` Marcel Apfelbaum
2015-10-18 12:20 ` Michael S. Tsirkin
2015-10-18 16:22 ` Andreas Färber
2015-10-19 15:47 ` Eduardo Habkost
2015-10-19 16:47 ` Andreas Färber [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=56251EB6.5000105@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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.