From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
Steve Muckle <smuckle@codeaurora.org>
Subject: Re: [RFC PATCH] msm: initial MSM8X60 early kernel boot support
Date: Mon, 21 Jun 2010 23:07:17 +0100 [thread overview]
Message-ID: <20100621220716.GD13624@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1277157793-9712-1-git-send-email-dwalker@codeaurora.org>
On Mon, Jun 21, 2010 at 03:03:13PM -0700, Daniel Walker wrote:
> +int boot_secondary(unsigned int cpu, struct task_struct *idle)
> +{
> + int cnt = 0;
> + printk(KERN_DEBUG "Starting secondary CPU %d\n", cpu);
> +
> + /* Tell other CPUs to come out or reset. Note that secondary CPUs
> + * are probably running with caches off, so we'll need to clean to
> + * memory. Normal cache ops will only clean to L2.
> + */
> + pen_release = cpu;
> + dmac_clean_range((void *)&pen_release,
> + (void *)(&pen_release + sizeof(pen_release)));
dmac_clean_range() and dmac_inv_range() no longer exist.
> + dmac_clean_range((void *)&secondary_data,
> + (void *)(&secondary_data + sizeof(secondary_data)));
We've already fixed this.
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] msm: initial MSM8X60 early kernel boot support
Date: Mon, 21 Jun 2010 23:07:17 +0100 [thread overview]
Message-ID: <20100621220716.GD13624@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1277157793-9712-1-git-send-email-dwalker@codeaurora.org>
On Mon, Jun 21, 2010 at 03:03:13PM -0700, Daniel Walker wrote:
> +int boot_secondary(unsigned int cpu, struct task_struct *idle)
> +{
> + int cnt = 0;
> + printk(KERN_DEBUG "Starting secondary CPU %d\n", cpu);
> +
> + /* Tell other CPUs to come out or reset. Note that secondary CPUs
> + * are probably running with caches off, so we'll need to clean to
> + * memory. Normal cache ops will only clean to L2.
> + */
> + pen_release = cpu;
> + dmac_clean_range((void *)&pen_release,
> + (void *)(&pen_release + sizeof(pen_release)));
dmac_clean_range() and dmac_inv_range() no longer exist.
> + dmac_clean_range((void *)&secondary_data,
> + (void *)(&secondary_data + sizeof(secondary_data)));
We've already fixed this.
next prev parent reply other threads:[~2010-06-21 22:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 21:40 [RFC PATCH] smp: parallel smp boot option Daniel Walker
2010-06-21 21:40 ` Daniel Walker
2010-06-21 22:00 ` Russell King - ARM Linux
2010-06-21 22:00 ` Russell King - ARM Linux
2010-06-21 22:07 ` Daniel Walker
2010-06-21 22:07 ` Daniel Walker
2010-06-21 22:22 ` Daniel Walker
2010-06-21 22:22 ` Daniel Walker
2010-06-21 22:31 ` Russell King - ARM Linux
2010-06-21 22:31 ` Russell King - ARM Linux
2010-06-22 0:47 ` smuckle
2010-06-22 0:47 ` smuckle at codeaurora.org
2010-06-22 0:23 ` smuckle
2010-06-22 0:23 ` smuckle at codeaurora.org
2010-06-21 22:03 ` [RFC PATCH] msm: initial MSM8X60 early kernel boot support Daniel Walker
2010-06-21 22:03 ` Daniel Walker
2010-06-21 22:07 ` Russell King - ARM Linux [this message]
2010-06-21 22:07 ` Russell King - ARM Linux
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=20100621220716.GD13624@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=smuckle@codeaurora.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.