mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, Huang Shijie <shijie@os.amperecomputing.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
	rafael@kernel.org, linux-arch@vger.kernel.org,
	gregkh@linuxfoundation.org, linux-arm-kernel@lists.infradead.org,
	arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] arm64: irq: set the correct node for VMAP stack
Date: Tue,  5 Dec 2023 15:16:36 +0000	[thread overview]
Message-ID: <170178641072.13754.15163791015207648414.b4-ty@kernel.org> (raw)
In-Reply-To: <20231124031513.81548-1-shijie@os.amperecomputing.com>

On Fri, 24 Nov 2023 11:15:13 +0800, Huang Shijie wrote:
> In current code, init_irq_stacks() will call cpu_to_node().
> The cpu_to_node() depends on percpu "numa_node" which is initialized in:
>      arch_call_rest_init() --> rest_init() -- kernel_init()
> 	--> kernel_init_freeable() --> smp_prepare_cpus()
> 
> But init_irq_stacks() is called in init_IRQ() which is before
> arch_call_rest_init().
> 
> [...]

Applied to arm64 (for-next/mm), thanks!

[1/1] arm64: irq: set the correct node for VMAP stack
      https://git.kernel.org/arm64/c/75b5e0bf90bf

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

      parent reply	other threads:[~2023-12-05 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  9:16 [PATCH] " Huang Shijie
2023-11-15 14:50 ` kernel test robot
2023-11-16 17:18 ` Catalin Marinas
2023-11-17  2:50   ` Shijie Huang
2023-11-18 15:47   ` [PATCH v2] " Huang Shijie
2023-11-18 16:02   ` [PATCH v3] " Huang Shijie
2023-11-23 16:55     ` Catalin Marinas
2023-11-24  3:15       ` [PATCH v4] " Huang Shijie
2023-11-24 11:47         ` Catalin Marinas
2023-12-05 15:16         ` Will Deacon [this message]

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=170178641072.13754.15163791015207648414.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-team@android.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=shijie@os.amperecomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®