From: Jan Kiszka <jan.kiszka@siemens.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michael Kelley <mhklinux@outlook.com>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Long Li <longli@microsoft.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Florian Bezdeka <florian.bezdeka@siemens.com>
Subject: Re: [PATCH] Drivers: hv: vmbus: Move add_interrupt_randomness back to real interrupt
Date: Tue, 17 Mar 2026 14:34:26 +0100 [thread overview]
Message-ID: <5262eafa-7f94-41c8-85d7-a2b8d7f27c5a@siemens.com> (raw)
In-Reply-To: <20260317132252.AJlwEyMh@linutronix.de>
On 17.03.26 14:22, Sebastian Andrzej Siewior wrote:
> On 2026-03-17 12:56:02 [+0100], Jan Kiszka wrote:
>>>> @@ -1410,6 +1408,8 @@ void vmbus_isr(void)
>>>> lockdep_hardirq_threaded();
>>>> __vmbus_isr();
>>>> }
>>>> +
>>>> + add_interrupt_randomness(vmbus_interrupt);
>>>> }
>>>> EXPORT_SYMBOL_FOR_MODULES(vmbus_isr, "mshv_vtl");
>>>
>>> Why not sysvec_hyperv_callback()?
>>
>> Because we do not want to be x86-only.
>
> Who is other one and does it have its add_interrupt_randomness() there
> already?
It's the arm64 path of the hv support. Regarding the vmbus IRQ, it seems
to be fully handled here, without an equivalent of
arch/x86/kernel/cpu/mshyperv.c.
> This is a driver, this does not belong here.
Don't argue with me, I didn't put it here in the beginning. Maybe
Michael can shed more light on this (and sorry for having forgotten to
CC you on this patch).
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2026-03-17 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 8:09 Jan Kiszka
2026-03-17 11:05 ` Sebastian Andrzej Siewior
2026-03-17 11:56 ` Jan Kiszka
2026-03-17 13:22 ` Sebastian Andrzej Siewior
2026-03-17 13:34 ` Jan Kiszka [this message]
2026-03-17 17:26 ` Michael Kelley
2026-03-18 10:10 ` Sebastian Andrzej Siewior
2026-03-19 3:39 ` Michael Kelley
2026-03-19 9:57 ` Sebastian Andrzej Siewior
2026-03-19 14:19 ` Michael Kelley
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=5262eafa-7f94-41c8-85d7-a2b8d7f27c5a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=bigeasy@linutronix.de \
--cc=decui@microsoft.com \
--cc=florian.bezdeka@siemens.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mhklinux@outlook.com \
--cc=wei.liu@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®