From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/6] ARM: mach-virt: add SMP support using PSCI
Date: Tue, 18 Dec 2012 10:49:27 +0000 [thread overview]
Message-ID: <20121218104927.GA9632@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1212171555570.1263@xanadu.home>
On Mon, Dec 17, 2012 at 09:45:52PM +0000, Nicolas Pitre wrote:
> On Mon, 17 Dec 2012, Will Deacon wrote:
> > This patch adds support for SMP to mach-virt using the PSCI
> > infrastructure.
> >
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
[...]
> > +/*
> > + * Enumerate the possible CPU set from the device tree.
> > + */
> > +static void __init virt_smp_init_cpus(void)
> > +{
> > + struct device_node *dn = NULL;
> > + int cpu = 0;
> > +
> > + while ((dn = of_find_node_by_type(dn, "cpu"))) {
> > + if (cpu < NR_CPUS)
> > + set_cpu_possible(cpu, true);
> > + cpu++;
> > + }
> > +
> > + /* sanity check */
> > + if (cpu > NR_CPUS)
> > + pr_warning("no. of cores (%d) greater than configured maximum "
> > + "of %d - clipping\n",
> > + cpu, NR_CPUS);
>
> Since commit 5587164eea you shouldn't need any of the above.
There's going to be nothing left at this rate! Thanks.
> > +#ifdef CONFIG_SMP
> > +extern struct smp_operations virt_smp_ops;
> > +#endif
>
> You don't need to surround prototype declaration here, unless your goal
> was to define a dummy virt_smp_ops when CONFIG_SMP is not selected?
> Otherwise the reference below would break compilation.
Right you are, the smp_ops macro does the magic for us. I'll put together a
v3.
Cheers,
Will
> > +
> > DT_MACHINE_START(VIRT, "Dummy Virtual Machine")
> > .init_irq = gic_init_irq,
> > .handle_irq = gic_handle_irq,
> > .timer = &virt_timer,
> > .init_machine = virt_init,
> > + .smp = smp_ops(virt_smp_ops),
> > .dt_compat = virt_dt_match,
> > MACHINE_END
> > --
> > 1.8.0
> >
>
next prev parent reply other threads:[~2012-12-18 10:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 16:35 [PATCH v2 0/6] Add support for a fake, para-virtualised machine Will Deacon
2012-12-17 16:35 ` [PATCH v2 1/6] ARM: opcodes: add missing include of linux/linkage.h Will Deacon
2012-12-17 16:35 ` [PATCH v2 2/6] ARM: opcodes: add opcodes definitions for ARM security extensions Will Deacon
2012-12-17 16:35 ` [PATCH v2 3/6] ARM: psci: add devicetree binding for describing PSCI firmware Will Deacon
2012-12-17 20:00 ` Arnd Bergmann
2012-12-18 10:08 ` Will Deacon
2012-12-17 16:35 ` [PATCH v2 4/6] ARM: psci: add support for PSCI invocations from the kernel Will Deacon
2012-12-17 20:51 ` Nicolas Pitre
2012-12-18 10:11 ` Will Deacon
2012-12-18 21:59 ` Nicolas Pitre
2012-12-19 11:27 ` Will Deacon
2012-12-17 16:35 ` [PATCH v2 5/6] ARM: Dummy Virtual Machine platform support Will Deacon
2012-12-18 12:04 ` [Xen-devel] " Stefano Stabellini
2012-12-18 13:14 ` Will Deacon
2012-12-18 13:32 ` Stefano Stabellini
2012-12-18 18:01 ` Christopher Covington
2012-12-18 18:18 ` Marc Zyngier
2012-12-19 15:25 ` Christopher Covington
2012-12-20 13:12 ` Stefano Stabellini
2012-12-20 13:25 ` Marc Zyngier
2012-12-17 16:35 ` [PATCH v2 6/6] ARM: mach-virt: add SMP support using PSCI Will Deacon
2012-12-17 21:45 ` Nicolas Pitre
2012-12-18 10:49 ` Will Deacon [this message]
2012-12-18 12:19 ` [Xen-devel] " Stefano Stabellini
2012-12-18 13:12 ` Marc Zyngier
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=20121218104927.GA9632@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.