From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: xenomai@lists.linux.dev, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH Dovetail 6.17 v3 1/4] clocksource/hyper-v: irq_pipeline: Enable pipelined clock events
Date: Tue, 21 Oct 2025 14:47:35 +0200 [thread overview]
Message-ID: <87a51kbevs.fsf@xenomai.org> (raw)
In-Reply-To: <20250602-flo-add-hyperv-support-for-6-15-v3-1-f3b45eaed2e8@siemens.com> (Florian Bezdeka's message of "Tue, 21 Oct 2025 14:23:11 +0200")
Florian Bezdeka <florian.bezdeka@siemens.com> writes:
> Make the clock event around the STIMER0 pipeline safe. The
> implementation is following the same pattern that we already have in
> place for the x86 LAPIC interrupt / clock event.
>
> To get the proxy tick working we need to link the hyperv clock event
> device with the STIMER0 vector. This part is also following the pattern
> of the x86 lapic interrupt. Both have a fixed arch specific vector
> assigned.
>
Series merged, thanks.
--
Philippe.
next prev parent reply other threads:[~2025-10-21 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 12:23 [PATCH Dovetail 6.17 v3 0/4] dovetail: Add support for hyper-v as hypervisor Florian Bezdeka
2025-10-21 12:23 ` [PATCH Dovetail 6.17 v3 1/4] clocksource/hyper-v: irq_pipeline: Enable pipelined clock events Florian Bezdeka
2025-10-21 12:47 ` Philippe Gerum [this message]
2025-10-21 12:23 ` [PATCH Dovetail 6.17 v3 2/4] x86: irq_pipeline: Implement inband handler for hyper-v specific vectors Florian Bezdeka
2025-10-21 12:23 ` [PATCH Dovetail 6.17 v3 3/4] hyper-v: x86: dovetail: Close race window in PV spinlocks Florian Bezdeka
2025-10-21 12:23 ` [PATCH Dovetail 6.17 v3 4/4] x86: irq_pipeline: Allow CONFIG_HYPERV in combination with CONFIG_DOVETAIL Florian Bezdeka
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=87a51kbevs.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@lists.linux.dev \
/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.