From: Bjorn Helgaas <helgaas@kernel.org>
To: korantwork@gmail.com
Cc: nirmal.patel@linux.intel.com, kbusch@kernel.org,
jonathan.derrick@linux.dev, lpieralisi@kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Xinghui Li <korantli@tencent.com>
Subject: Re: [PATCH v5] PCI: vmd: Add the module param to adjust MSI mode
Date: Fri, 28 Apr 2023 14:58:22 -0500 [thread overview]
Message-ID: <20230428195822.GA361074@bhelgaas> (raw)
In-Reply-To: <20230428184036.GA298937@bhelgaas>
On Fri, Apr 28, 2023 at 01:40:36PM -0500, Bjorn Helgaas wrote:
> On Thu, Apr 20, 2023 at 03:09:14PM +0800, korantwork@gmail.com wrote:
> > From: Xinghui Li <korantli@tencent.com>
> What if you made boolean parameters like these:
>
> no_msi_remap
>
> If the VMD supports it, disable VMD MSI-X remapping. This
> improves interrupt performance because child device interrupts
> avoid the VMD MSI-X domain interrupt handler.
>
> msi_remap
>
> Remap child MSI-X interrupts into VMD MSI-X interrupts. This
> limits the number of MSI-X vectors available to the whole child
> device domain to the number of VMD MSI-X interrupts.
I guess having two parameters that affect the same feature is also
confusing. Maybe just "msi_remap=0" or "msi_remap=1" or something?
I think what makes "disable_msi_bypass=0" hard is that "MSI bypass" by
itself is a negative feature (the positive activity is MSI remapping),
and disabling bypass gets us back to the positive "MSI remapping"
situation, and "disable_msi_bypass=0" negates that again, so we're
back to ... uh ... let's see ... we are not disabling the bypass of
MSI remapping, so I guess MSI remapping would be *enabled*? Is that
right?
Bjorn
next prev parent reply other threads:[~2023-04-28 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 7:09 [PATCH v5] PCI: vmd: Add the module param to adjust MSI mode korantwork
2023-04-28 18:40 ` Bjorn Helgaas
2023-04-28 19:58 ` Bjorn Helgaas [this message]
2023-05-05 9:31 ` Xinghui Li
2023-05-05 16:07 ` Bjorn Helgaas
2023-05-08 13:01 ` Xinghui Li
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=20230428195822.GA361074@bhelgaas \
--to=helgaas@kernel.org \
--cc=jonathan.derrick@linux.dev \
--cc=kbusch@kernel.org \
--cc=korantli@tencent.com \
--cc=korantwork@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=nirmal.patel@linux.intel.com \
/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