linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: smp: Fix Unknown IPI message 0x1
Date: Mon, 17 Jan 2011 18:01:31 +0530	[thread overview]
Message-ID: <d93218062aa1e6948453d1ddd5b9e2b0@mail.gmail.com> (raw)
In-Reply-To: <1295267193.21557.14.camel@e102109-lin.cambridge.arm.com>

> -----Original Message-----
> From: Catalin Marinas [mailto:catalin.marinas at arm.com]
> Sent: Monday, January 17, 2011 5:57 PM
> To: Russell King - ARM Linux
> Cc: Santosh Shilimkar; linux-arm-kernel at lists.infradead.org
> Subject: Re: [PATCH] ARM: smp: Fix Unknown IPI message 0x1
>
> On Mon, 2011-01-17 at 12:19 +0000, Russell King - ARM Linux wrote:
> > On Mon, Jan 17, 2011 at 05:38:11PM +0530, Santosh Shilimkar wrote:
> > > This should be ok. May be Catalin can comment on choice of SGI1
> in
> > > generic smp_cross_call().
> >
> > It's something that came from ARMs early SMP work (in 2002 iirc),
> and
> > was carried forward.  What I don't know is whether there was any
> boot
> > protocol documentation produced which said "you will wait for any
> SGI"
> > or "you will wait for SGI1".
>
> At least on the ARM Ltd platforms, the boot monitor waits for any
> interrupt (it is in WFI). I can't tell about other platforms.
>
Same for OMAP4. Any SGI will do.

Regards,
Santosh

  reply	other threads:[~2011-01-17 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 11:56 [PATCH] ARM: smp: Fix Unknown IPI message 0x1 Santosh Shilimkar
2011-01-17 12:01 ` Russell King - ARM Linux
2011-01-17 12:08   ` Santosh Shilimkar
2011-01-17 12:19     ` Russell King - ARM Linux
2011-01-17 12:26       ` Catalin Marinas
2011-01-17 12:31         ` Santosh Shilimkar [this message]
2011-01-17 12:34           ` Russell King - ARM Linux
2011-01-21 22:29             ` Jeff Ohlstein

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=d93218062aa1e6948453d1ddd5b9e2b0@mail.gmail.com \
    --to=santosh.shilimkar@ti.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 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).