From: Marc Zyngier <maz@kernel.org>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Julien Thierry <julien.thierry@arm.com>
Subject: Re: [PATCH] arm64/irq: use NMI to send stop IPI
Date: Mon, 14 Dec 2020 09:46:55 +0000 [thread overview]
Message-ID: <f26972235231d9ee59a948db2b10efd0@kernel.org> (raw)
In-Reply-To: <CAFgQCTvLud2qOWfSDK_HbKwid-2uLPDA_Uz-iTQzBYiWwqJX5Q@mail.gmail.com>
On 2020-12-14 02:20, Pingfan Liu wrote:
[...]
> After serval days of chasing this issue, I have a raw idea about it.
> What about re-structure the code like
> DEFINE_IDTENTRY_SYSVEC_SIMPLE(sysvec_reschedule_ipi) ?
I'm not sure how you want to mimic what x86 does, given that we have
at least three different root interrupt controllers on arm64 (plus
a fourth coming up), all of which have access methods that are not
part of the CPU architecture, and that are shared with the 32bit
part.
> I will send a series soon afterward.
Please wait until the merge window is over.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-14 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 13:14 [PATCH] arm64/irq: use NMI to send stop IPI Pingfan Liu
2020-12-08 14:04 ` Marc Zyngier
2020-12-14 2:20 ` Pingfan Liu
2020-12-14 2:25 ` [PATCH 1/3] kernel/irq: __handle_domain_irq() makes irq_enter/exit arch optional Pingfan Liu
2020-12-14 2:25 ` [PATCH 2/3] arm64/irq-gic-v3: make gic_handle_irq() cope with enter_from_kernel_mode() Pingfan Liu
2020-12-14 2:25 ` [PATCH 3/3] arm64/irq-gic-v3: make reschedule-ipi light weight Pingfan Liu
2020-12-14 9:46 ` Marc Zyngier [this message]
2020-12-14 13:04 ` [PATCH] arm64/irq: use NMI to send stop IPI Pingfan Liu
2020-12-14 13:24 ` Marc Zyngier
2020-12-15 5:40 ` Pingfan Liu
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=f26972235231d9ee59a948db2b10efd0@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=julien.thierry@arm.com \
--cc=kernelfans@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.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.