mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jan Kiszka <jan.kiszka@siemens.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:22:52 +0100	[thread overview]
Message-ID: <20260317132252.AJlwEyMh@linutronix.de> (raw)
In-Reply-To: <f718a22c-bbf2-4206-ba7d-391243c84f60@siemens.com>

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?
This is a driver, this does not belong here.

> Jan

Sebastian

  reply	other threads:[~2026-03-17 13:22 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 [this message]
2026-03-17 13:34       ` Jan Kiszka
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=20260317132252.AJlwEyMh@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=decui@microsoft.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=haiyangz@microsoft.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longli@microsoft.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®