mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Michael Kelley <mikelley@microsoft.com>,
	sthemmin@microsoft.com, kys@microsoft.com, wei.liu@kernel.org,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	hpa@zytor.com, arnd@arndb.de, linux-hyperv@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH v3 10/10] clocksource/drivers/hyper-v: Move handling of STIMER0 interrupts
Date: Tue, 2 Mar 2021 23:18:40 +0100	[thread overview]
Message-ID: <5495b52c-e619-90c4-0c4f-fdbde9e1ce58@linaro.org> (raw)
In-Reply-To: <1614721102-2241-11-git-send-email-mikelley@microsoft.com>

On 02/03/2021 22:38, Michael Kelley wrote:
> STIMER0 interrupts are most naturally modeled as per-cpu IRQs. But
> because x86/x64 doesn't have per-cpu IRQs, the core STIMER0 interrupt
> handling machinery is done in code under arch/x86 and Linux IRQs are
> not used. Adding support for ARM64 means adding equivalent code
> using per-cpu IRQs under arch/arm64.
> 
> A better model is to treat per-cpu IRQs as the normal path (which it is
> for modern architectures), and the x86/x64 path as the exception. Do this
> by incorporating standard Linux per-cpu IRQ allocation into the main
> SITMER0 driver code, and bypass it in the x86/x64 exception case. For
> x86/x64, special case code is retained under arch/x86, but no STIMER0
> interrupt handling code is needed under arch/arm64.
> 
> No functional change.
> 
> Signed-off-by: Michael Kelley <mikelley@microsoft.com>

Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>

[ ... ]

-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2021-03-02 23:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 21:38 [PATCH v3 00/10] Refactor arch specific Hyper-V code Michael Kelley
2021-03-02 21:38 ` [PATCH v3 01/10] Drivers: hv: vmbus: Move Hyper-V page allocator to arch neutral code Michael Kelley
2021-03-02 21:38 ` [PATCH v3 02/10] x86/hyper-v: Move hv_message_type to architecture neutral module Michael Kelley
2021-03-02 21:38 ` [PATCH v3 03/10] Drivers: hv: Redo Hyper-V synthetic MSR get/set functions Michael Kelley
2021-03-02 21:38 ` [PATCH v3 04/10] Drivers: hv: vmbus: Move hyperv_report_panic_msg to arch neutral code Michael Kelley
2021-03-02 21:38 ` [PATCH v3 05/10] Drivers: hv: vmbus: Handle auto EOI quirk inline Michael Kelley
2021-03-02 21:38 ` [PATCH v3 06/10] Drivers: hv: vmbus: Move handling of VMbus interrupts Michael Kelley
2021-03-02 21:38 ` [PATCH v3 07/10] clocksource/drivers/hyper-v: Handle vDSO differences inline Michael Kelley
2021-03-02 22:14   ` Daniel Lezcano
2021-03-02 23:06     ` Michael Kelley
2021-03-08 13:49       ` Michael Kelley
2021-03-08 14:41         ` Daniel Lezcano
2021-03-02 21:38 ` [PATCH v3 08/10] clocksource/drivers/hyper-v: Handle sched_clock " Michael Kelley
2021-03-02 22:15   ` Daniel Lezcano
2021-03-02 21:38 ` [PATCH v3 09/10] clocksource/drivers/hyper-v: Set clocksource rating based on Hyper-V feature Michael Kelley
2021-03-02 21:38 ` [PATCH v3 10/10] clocksource/drivers/hyper-v: Move handling of STIMER0 interrupts Michael Kelley
2021-03-02 22:18   ` Daniel Lezcano [this message]
2021-03-08 16:48 ` [PATCH v3 00/10] Refactor arch specific Hyper-V code Wei 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=5495b52c-e619-90c4-0c4f-fdbde9e1ce58@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=kys@microsoft.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=mingo@redhat.com \
    --cc=sthemmin@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=wei.liu@kernel.org \
    --cc=x86@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 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®