All of lore.kernel.org
 help / color / mirror / Atom feed
From: vaibhav shinde <v.bhav.shinde@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: trisha yad <trisha1march@gmail.com>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: DEBUG_STACKOVERFLOW issue on ARM
Date: Thu, 11 Oct 2012 13:09:46 +0530	[thread overview]
Message-ID: <CAB5gotsV-yOU6F2n_-HhVmheMKFX1miyw6yZMogV7+kKe4Jggw@mail.gmail.com> (raw)
In-Reply-To: <20121005083113.GG4625@n2100.arm.linux.org.uk>

Hi Russel,

On Fri, Oct 5, 2012 at 2:01 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
>
> On Wed, Oct 03, 2012 at 05:18:56PM +0530, trisha yad wrote:
> > I wish to know how can I support this function in 3.0 ?
>
> If your description is correct, then all you need to do is to ensure
> that you route interrupts to other CPUs.
>
> You can do that by running the userspace irqbalance daemon.
>

I also tried with the irqbalance daemon, on ARM quad core architecture,
and as per my understanding, the daemon sets the
/proc/irq/<irq.no.>/smp_affinity
file according to the irq frequency on a particular processor.

          However, the daemon doesn't work as expected, I also tried
accessing the
proc file mentioned above to set the cpu mask for particular irq, but this
just block the processing of the irq, as I see the count of that irq
doesnt increase
in /proc/interrupts.

            My conclusion is that the irqbalancing is not supported on
ARM arch or there is
something  more required for this to work. Kindly provide some
pointers over this.

Regards,
Vaibhav

  reply	other threads:[~2012-10-11  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 11:48 DEBUG_STACKOVERFLOW issue on ARM trisha yad
2012-10-05  8:31 ` Russell King - ARM Linux
2012-10-11  7:39   ` vaibhav shinde [this message]
2012-10-11  8:01     ` 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=CAB5gotsV-yOU6F2n_-HhVmheMKFX1miyw6yZMogV7+kKe4Jggw@mail.gmail.com \
    --to=v.bhav.shinde@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=ralf@linux-mips.org \
    --cc=trisha1march@gmail.com \
    /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.