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] Add call to non-crashing cores through IPI
Date: Mon, 22 Nov 2010 22:55:46 +0530	[thread overview]
Message-ID: <bdbc2959fe609090afc0fb6d656e36de@mail.gmail.com> (raw)
In-Reply-To: <20101122142101.GL31227@n2100.arm.linux.org.uk>

> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> Sent: Monday, November 22, 2010 7:51 PM
> To: Santosh Shilimkar
> Cc: Per Fransson; Mika Westerberg; kexec at lists.infradead.org; linux-arm-
> kernel at lists.infradead.org
> Subject: Re: [PATCH] Add call to non-crashing cores through IPI
>
> On Mon, Nov 22, 2010 at 06:37:09PM +0530, Santosh Shilimkar wrote:
> > > ARM: smp: make smp_send_stop() wait for secondary CPUs to stop
> > >
> > > Wait up to one second for secondary CPUs to respond to a request to
> > > stop.  This avoids the sender CPU continuing and possibly destroying
> > > state before the recipients have had a chance to respond to the
stop.
> > > However, if the recipients have crashed, we won't hang the sender
> > > CPU indefinitely.
> > >
> > Just tried this patch thinking it might fix the reboot issue
> > reported earlier. But it doesn't help.
>
> I was hoping that it might change the behaviour slightly, but if not
> the patch can't do any harm.
>
> The reboot stuff works fine on Versatile Express with Cortex A9, so
> I suspect your problem might be specific to OMAP.
Interesting.
I thought it's a common issue. Will have a look at it more
closely

  reply	other threads:[~2010-11-22 17:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 10:08 [PATCH] Add call to non-crashing cores through IPI Per Fransson
2010-11-22  7:24 ` Mika Westerberg
2010-11-22  9:47   ` Maxim Uvarov
2010-11-22  9:53   ` Per Fransson
2010-11-22 10:47     ` Russell King - ARM Linux
2010-11-22 11:27       ` Russell King - ARM Linux
2010-11-22 13:07         ` Santosh Shilimkar
2010-11-22 14:21           ` Russell King - ARM Linux
2010-11-22 17:25             ` Santosh Shilimkar [this message]
2010-11-22 14:31         ` Per Fransson
2010-11-22 14:40           ` Russell King - ARM Linux
2010-11-22 17:03             ` Per Fransson
2010-11-22 17:12               ` Catalin Marinas
2010-11-22 20:09                 ` Maxim Uvarov
2010-11-22 22:14                   ` Per Fransson
2010-11-22 22:30                     ` Per Fransson
2010-11-23  9:14                   ` Catalin Marinas
2010-11-23 10:57                     ` Per Fransson
2010-11-23 12:37                       ` Catalin Marinas
2010-11-23 12:41                         ` Mika Westerberg
2010-11-23 12:48                           ` Catalin Marinas
2010-11-23 13:01                             ` Maxim Uvarov
2010-11-23 16:31                               ` Per Fransson

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=bdbc2959fe609090afc0fb6d656e36de@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).