public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v8 9/4] arm64: remove irq_count and do_softirq_own_stack()
Date: Mon, 21 Dec 2015 12:21:48 +0000	[thread overview]
Message-ID: <20151221122148.GK23092@arm.com> (raw)
In-Reply-To: <DB3PR08MB0041F2F26E5FABEE61ACA089F3E40@DB3PR08MB0041.eurprd08.prod.outlook.com>

On Mon, Dec 21, 2015 at 12:19:32PM +0000, James Morse wrote:
> Will Deacon wrote:
> >> > +   mrs     x26, sp_el0             // already masked
> >>
> >> Nit: How about using 'get_thread_info x26'?
> > 
> > Something like the following?
> 
> Looks fine - I guess you're cleverly leaving the the el0_irq case to be
> covered by get_thread_info in kernel_entry?

Yup. tsk is always valid for exceptions taken from el0, afaict.

Will

  reply	other threads:[~2015-12-21 12:21 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 11:02 [PATCH v8 0/4] arm64: Add support for IRQ stack James Morse
2015-12-04 11:02 ` [PATCH v8 1/4] arm64: Store struct task_info in sp_el0 James Morse
2015-12-04 13:27   ` Catalin Marinas
2015-12-04 14:55     ` James Morse
2015-12-04 16:18       ` Catalin Marinas
2015-12-06 13:15     ` Jungseok Lee
2015-12-04 11:02 ` [PATCH v8 2/4] arm64: Modify stack trace and dump for use with irq_stack James Morse
2015-12-04 12:21   ` Jungseok Lee
2015-12-04 14:31   ` Catalin Marinas
2015-12-04 11:02 ` [PATCH v8 3/4] arm64: Add do_softirq_own_stack() and enable irq_stacks James Morse
2015-12-04 13:46   ` Catalin Marinas
2015-12-04 13:47     ` Catalin Marinas
2015-12-07 22:48   ` Catalin Marinas
2015-12-08 11:43     ` Will Deacon
2015-12-08 16:02       ` Jungseok Lee
2015-12-08 17:23         ` James Morse
2015-12-08 17:27           ` Will Deacon
2015-12-08 23:13           ` Jungseok Lee
2015-12-09  9:47           ` James Morse
2015-12-09 11:38             ` Will Deacon
2015-12-09 13:45   ` Will Deacon
2015-12-09 14:36     ` James Morse
2015-12-04 11:02 ` [PATCH v8 4/4] arm64: switch to irq_stack during softirq James Morse
2015-12-04 14:01   ` Catalin Marinas
2015-12-04 14:39     ` James Morse
2015-12-04 18:40       ` Catalin Marinas
2015-12-08 10:29         ` James Morse
2015-12-06 13:51       ` Jungseok Lee
2015-12-04 12:17 ` [PATCH v8 0/4] arm64: Add support for IRQ stack Jungseok Lee
2015-12-06 13:56   ` Jungseok Lee
2015-12-04 13:57 ` Catalin Marinas
2015-12-06 13:33   ` Jungseok Lee
2015-12-10 10:22 ` [PATCH v8 5/4] arm64: Fix off-by-one in stack tracing when stepping off irq stack James Morse
2015-12-10 10:22   ` [PATCH v8 6/4] arm64: Add this_cpu_ptr() assembler macro for use in entry.S James Morse
2015-12-10 10:22   ` [PATCH v8 7/4] arm64: when walking onto the task stack, check sp & fp are in current->stack James Morse
2015-12-10 10:22   ` [PATCH v8 8/4] arm64: don't call C code with el0's fp register James Morse
2015-12-10 14:03   ` [PATCH v8 5/4] arm64: Fix off-by-one in stack tracing when stepping off irq stack Jungseok Lee
2015-12-15 11:21 ` [PATCH v8 9/4] arm64: reduce stack use in irq_handler James Morse
2015-12-18 16:01 ` [PATCH v8 9/4] arm64: remove irq_count and do_softirq_own_stack() James Morse
2015-12-20 11:07   ` Jungseok Lee
2015-12-21 11:30     ` Will Deacon
2015-12-21 12:19       ` James Morse
2015-12-21 12:21         ` Will Deacon [this message]
2015-12-21 14:06           ` Jungseok Lee

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=20151221122148.GK23092@arm.com \
    --to=will.deacon@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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