From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: peter.maydell@linaro.org, agraf@suse.de, qemu-devel@nongnu.org,
borntraeger@de.ibm.com, imammedo@redhat.com, pbonzini@redhat.com,
afaerber@suse.de, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [RFC PATCH v0 8/9] target-i386: Set apic_id during CPU initfn
Date: Tue, 15 Dec 2015 13:44:47 +0530 [thread overview]
Message-ID: <20151215081447.GH18759@in.ibm.com> (raw)
In-Reply-To: <20151214174406.GE3774@thinpad.lan.raisama.net>
On Mon, Dec 14, 2015 at 03:44:06PM -0200, Eduardo Habkost wrote:
> On Thu, Dec 10, 2015 at 11:45:43AM +0530, Bharata B Rao wrote:
> > Move back the setting of apic_id to instance_init routine (x86_cpu_initfn)
> > This is needed to initialize X86 CPUs using generic cpu-package device.
>
> Could you explain where exactly apic_id will be used, to make it
> necessary to initialize it earlier?
There is a check in x86_cpu_realizefn() to see if apic_id has been
initialized properly. Hence I thought x86 target will require apic_id
to have been initialized before CPU realization and that is what
the existing code does via pc_cpus_init() and pc_new_cpu(). i.e.,
apic_id property is set before setting the realize property to true.
However...
>
> >
> > TODO: I am not fully aware of the general direction in which apic_id
> > changes in X86 have evolved and hence not sure if this is indeed aligned with
> > the X86 way of doing things. This is just to help the PoC implementation
> > that I have in this patchset to convert PC CPUs initialization into
> > cpu-package device based initialization.
>
> You shouldn't initialize apic_id on initfn. APIC ID depends (and
> will depend) on different CPU properties related to topology,
> including (but not limited to) CPU index and CPU topology
> properties we may introduce in the future, so it should be done
> later (at realize time), not on initfn.
... with the current patchset, I just experimented now by moving the setting
of apic_id to x86_cpu_realizefn() and things work just fine. I was in fact
pleasantly surprised to see that I could hot add a cpu core by hot plugging
the cpu-core device on x86 too.
>
> Also, cpu_index is initialized by cpu_exec_init(), and
> cpu_exec_init() must not be called by initfn. The cpu_exec_init()
> call should (and will) be moved to realize in x86 and all other
> architectures.
Right, I have already moved cpu_exec_init() call to realizefn for PowerPC.
Regards,
Bharata.
next prev parent reply other threads:[~2015-12-15 8:15 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 6:15 [Qemu-devel] [RFC PATCH v0 0/9] Generic cpu-core device Bharata B Rao
2015-12-10 6:15 ` [Qemu-devel] [RFC PATCH v0 1/9] vl: Don't allow CPU toplogies with partially filled cores Bharata B Rao
2015-12-10 10:25 ` Daniel P. Berrange
2015-12-11 3:24 ` Bharata B Rao
2015-12-14 17:37 ` Eduardo Habkost
2015-12-15 8:41 ` Bharata B Rao
2015-12-10 6:15 ` [Qemu-devel] [RFC PATCH v0 2/9] cpu: Store CPU typename in MachineState Bharata B Rao
2015-12-14 17:29 ` Eduardo Habkost
2015-12-15 8:38 ` Bharata B Rao
2015-12-15 15:31 ` Eduardo Habkost
2015-12-16 16:54 ` Igor Mammedov
2015-12-16 19:39 ` Eduardo Habkost
2015-12-16 22:26 ` Igor Mammedov
2015-12-17 18:09 ` Eduardo Habkost
2015-12-18 10:46 ` Igor Mammedov
2015-12-18 15:51 ` Eduardo Habkost
2015-12-18 16:01 ` Igor Mammedov
2015-12-10 6:15 ` [Qemu-devel] [RFC PATCH v0 3/9] cpu: Don't realize CPU from cpu_generic_init() Bharata B Rao
2015-12-10 6:15 ` [Qemu-devel] [RFC PATCH v0 4/9] cpu: CPU socket backend Bharata B Rao
2015-12-10 6:15 ` [Qemu-devel] [RFC PATCH v0 5/9] vl: Create CPU socket backend objects Bharata B Rao
2015-12-10 6:15 ` [Qemu-devel] [RFC PATCH v0 6/9] cpu: Introduce CPU core device Bharata B Rao
2015-12-10 6:15 ` [Qemu-devel] [RFC PATCH v0 7/9] spapr: Convert boot CPUs into CPU core device initialization Bharata B Rao
2015-12-10 6:15 ` [Qemu-devel] [RFC PATCH v0 8/9] target-i386: Set apic_id during CPU initfn Bharata B Rao
2015-12-14 17:44 ` Eduardo Habkost
2015-12-15 8:14 ` Bharata B Rao [this message]
2015-12-10 6:15 ` [Qemu-devel] [RFC PATCH v0 9/9] pc: Convert boot CPUs into CPU core device initialization Bharata B Rao
2015-12-10 12:35 ` [Qemu-devel] [RFC PATCH v0 0/9] Generic cpu-core device Igor Mammedov
2015-12-11 3:57 ` Bharata B Rao
2015-12-15 5:27 ` Zhu Guihua
2015-12-16 15:16 ` Andreas Färber
2015-12-16 15:11 ` Igor Mammedov
2015-12-17 9:19 ` Peter Krempa
2015-12-16 15:46 ` Andreas Färber
2015-12-16 21:58 ` Igor Mammedov
2015-12-24 1:59 ` Zhu Guihua
2015-12-29 13:52 ` Igor Mammedov
2016-01-01 3:47 ` Bharata B Rao
2016-01-04 12:52 ` Igor Mammedov
2015-12-10 20:25 ` Matthew Rosato
2015-12-14 6:25 ` Bharata B Rao
2015-12-16 15:19 ` Andreas Färber
2015-12-16 15:44 ` Igor Mammedov
2015-12-16 15:57 ` Andreas Färber
2015-12-16 17:22 ` Igor Mammedov
2015-12-16 22:37 ` Igor Mammedov
2016-01-12 3:54 ` David Gibson
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=20151215081447.GH18759@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).