mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Kelley <mhklinux@outlook.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "haiyangz@microsoft.com" <haiyangz@microsoft.com>,
	"wei.liu@kernel.org" <wei.liu@kernel.org>,
	"decui@microsoft.com" <decui@microsoft.com>,
	"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
	"kwilczynski@kernel.org" <kwilczynski@kernel.org>,
	"mani@kernel.org" <mani@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: RE: [PATCH v3 1/1] PCI: hv: Spread load across CPUs when selecting effective affinity CPU
Date: Wed, 28 Oct 2026 18:49:46 +0000	[thread overview]
Message-ID: <MN2PR02MB68636BDF288A70BDBACDC2D1D46F2@MN2PR02MB6863.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20261028171348.GA560291@bhelgaas>

From: Bjorn Helgaas <helgaas@kernel.org> Sent: Wednesday, October 28, 2026 10:14 AM
> 
> On Wed, Oct 28, 2026 at 08:55:59AM -0700, Michael Kelley wrote:
> > In a system with multiple devices with the same configuration (such as
> > NVMe controllers), the affinity masks are the same for all such devices.
> > Linux typicaly must select a single CPU from each mask to be the effective
> 
> s/typicaly/typically/
> 
> > @@ -881,25 +1016,48 @@ static int hv_pci_vec_irq_domain_alloc(struct irq_domain  *domain,
> >  }
> >
> >  /*
> > - * Pick the first cpu as the irq affinity that can be temporarily used for
> > + * Pick the first CPU as the irq affinity that can be temporarily used for
> 
> s/irq/IRQ/ if you want to follow the majority usage in this file, also
> below
> 
> >   * composing MSI from the hypervisor. GIC will eventually set the right
> >   * affinity for the irq and the 'unmask' will retarget the interrupt to that
> > - * cpu.
> > + * CPU.

Thanks. I'll fix these. My own preference is for "IRQ" anyway.

Michael



      reply	other threads:[~2026-10-28 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 15:55 Michael Kelley
2026-10-28 17:13 ` Bjorn Helgaas
2026-10-28 18:49   ` Michael Kelley [this message]

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=MN2PR02MB68636BDF288A70BDBACDC2D1D46F2@MN2PR02MB6863.namprd02.prod.outlook.com \
    --to=mhklinux@outlook.com \
    --cc=bhelgaas@google.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=helgaas@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=robh@kernel.org \
    --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®