All of lore.kernel.org
 help / color / mirror / Atom feed
From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 3/3] arm64: Add do_softirq_own_stack() and enable irq_stacks
Date: Fri, 04 Dec 2015 11:00:19 +0000	[thread overview]
Message-ID: <56617243.5050602@arm.com> (raw)
In-Reply-To: <20151127114715.GA25499@e104818-lin.cambridge.arm.com>

On 27/11/15 11:47, Catalin Marinas wrote:
> With this approach, we could run softirq either on the IRQ stack or on
> the process stack. One such process is softirqd, so there shouldn't be a
> problem since its goal is to run softirqs. But do_softirq() may be
> invoked from other contexts (network stack), I'm not sure what the stack
> looks like at that point.

As long as we don't reduce the stack sizes yet - nothing has changed. We
already run __do_softirq() on other task's stacks via __irq_exit().


> We could just do like x86 and always switch to the IRQ stack before
> invoking __do_softirq(). I don't think we lose much.

I will add an extra patch to do this - its not as straight forward as I
would like - as both ksoftirqd and softirq on irq_stack call
do_softirq_own_stack() with irq_count == 0.


Thanks,

James

  parent reply	other threads:[~2015-12-04 11:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 18:22 [PATCH v7 0/3] arm64: Add support for IRQ stack James Morse
2015-11-16 18:22 ` [PATCH v7 1/3] arm64: Add irq_stack boiler plate, store struct task_info in sp_el0 James Morse
2015-11-28 16:32   ` Jungseok Lee
2015-12-04 11:00     ` James Morse
2015-11-16 18:22 ` [PATCH v7 2/3] arm64: Modify stack trace and dump for use with irq_stack James Morse
2015-11-16 18:22 ` [PATCH v7 3/3] arm64: Add do_softirq_own_stack() and enable irq_stacks James Morse
2015-11-19 14:26   ` Jungseok Lee
2015-11-27 11:47     ` Catalin Marinas
2015-11-27 15:37       ` Jungseok Lee
2015-11-27 17:38         ` Catalin Marinas
2015-11-28 16:04           ` Jungseok Lee
2015-12-04 11:00       ` James Morse [this message]
2015-12-04 13:12         ` Catalin Marinas
2015-12-08 10:11           ` James Morse
2015-11-27 15:09   ` Catalin Marinas

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=56617243.5050602@arm.com \
    --to=james.morse@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.