[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220608122529.ub4knslhufwwsmhn@liuwe-devbox-debian-v2>
Date: Wed, 8 Jun 2022 12:25:29 +0000
From: Wei Liu <wei.liu@...nel.org>
To: "Michael Kelley (LINUX)" <mikelley@...rosoft.com>
Cc: Saurabh Sengar <ssengar@...ux.microsoft.com>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
"wei.liu@...nel.org" <wei.liu@...nel.org>,
Dexuan Cui <decui@...rosoft.com>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Saurabh Singh Sengar <ssengar@...rosoft.com>
Subject: Re: [RESEND PATCH v2] Drivers: hv: vmbus: Don't assign VMbus channel
interrupts to isolated CPUs
On Sat, May 28, 2022 at 01:11:21PM +0000, Michael Kelley (LINUX) wrote:
> From: Saurabh Sengar <ssengar@...ux.microsoft.com> Sent: Friday, May 27, 2022 12:44 AM
> >
> > When initially assigning a VMbus channel interrupt to a CPU, don’t choose
> > a managed IRQ isolated CPU (as specified on the kernel boot line with
> > parameter 'isolcpus=managed_irq,<#cpu>'). Also, when using sysfs to change
> > the CPU that a VMbus channel will interrupt, don't allow changing to a
> > managed IRQ isolated CPU.
> >
> > Signed-off-by: Saurabh Sengar <ssengar@...ux.microsoft.com>
> > ---
[...]
> Reviewed-by: Michael Kelley <mikelley@...rosoft.com>
Applied to hyperv-fixes. Thanks.
Powered by blists - more mailing lists