All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Xinghui Li <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 v4] PCI: vmd: Add the module param to adjust MSI mode
Date: Mon, 17 Apr 2023 16:44:59 -0500	[thread overview]
Message-ID: <20230417214459.GA53460@bhelgaas> (raw)
In-Reply-To: <CAEm4hYU4Z+LzhC8PT3OTePMeYjDa-QZEfXMkZqODnSY5i+_hrQ@mail.gmail.com>

On Mon, Apr 17, 2023 at 05:15:00PM +0800, Xinghui Li wrote:
> Friendly ping~

We had quite a bit of discussion that I don't see reflected in the
latest patch, so we're waiting on a v5 patch that addresses the
comments.

> On Tue, Apr 4, 2023 at 7:02 PM Xinghui Li <korantwork@gmail.com> wrote:
> >
> > On Tue, Apr 4, 2023 at 6:45 AM Bjorn Helgaas <helgaas@kernel.org> wrote:
> > >
> > > > In the patch I send in last email, We speculate that the VMD
> > > > Controller aggregate interrupts,
> > > > making the PCIe port less stressed and improving iops. In this
> > > > case(lots of 4k random IO), if we enable the VMD MSI
> > > > remapping, we found the interrupts from VMD Controller's MSI are less
> > > > and the IOPS is much higher.
> > >
> > > Great, that's useful information about why users would want to use
> > > this parameter.
> > >
> > > Obviously the other half is to mention the reasons why they may not be
> > > able to use it.  If "msi_remap=off" were *always* safe and desirable,
> > > we would just do that unconditionally and there would be no point in a
> > > parameter.
> > >
> > > > > > I place the "vmd_config_msi_remap_param" that is VMD MSI-X's mode
> > > > > > param configuring helper front
> > > > > > "vmd_enable_domain". So, It will not change the logic disabling
> > > > > > remapping from ee81ee84f873, such as
> > > > > > "Currently MSI remapping must be enabled in guest passthrough mode".
> > > > > > So, if the user config the wrong type, it will not work, and they can
> > > > > > find it by dmesg.
> > > > >
> > > > > That's kind of a problem.  I'm not in favor of something failing and
> > > > > the user having to debug it via dmesg.  That causes user frustration
> > > > > and problem reports.
> > > >
> > > > What about adding a sysfs node for it in VMD PCI bus dir, which allows
> > > > users to catch VMD's MSI current working mode?
> > >
> > > No, a sysfs node is not the answer to this.  If we *can* avoid a
> > > non-working situation, we should avoid it.  If users see a non-working
> > > situation, they will rightly complain, and somebody will have to debug
> > > it.  We don't want that.
> > emm~
> > I privately suppose: In the traditional way without module parameters,
> > this problem also exists. If the user disables remapping in guest os, the VMD
> > driver will force it to remapping mode.
> > What about I add the additional description in MODULE_PARM_DESC and comment?
> > As for some devices not support disable remapping,  What about changing
> > the param to disabae_bypass=0/1?
> > And make it clear in the description:
> > this parameter will only affect the disabling of bypass mode on
> > devices that support it.
> > >
> > > My point is that apparently guest passthrough mode is relevant and
> > > maybe it should be part of the commit log about how this parameter
> > > should be used.
> > You are right~
> > I will add some clarification on how to configure VMD MSI in the guest.
> > >
> > > Bjorn

  reply	other threads:[~2023-04-17 21:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 13:23 [PATCH v4] PCI: vmd: Add the module param to adjust MSI mode korantwork
2023-03-27  6:39 ` Xinghui Li
2023-03-28 21:34 ` Bjorn Helgaas
2023-03-29  8:57   ` Xinghui Li
2023-03-29 16:31     ` Bjorn Helgaas
2023-03-30  6:49       ` Patel, Nirmal
2023-04-02 14:34         ` Xinghui Li
2023-04-03 21:00           ` Patel, Nirmal
2023-04-02 15:02       ` Xinghui Li
2023-04-03 22:45         ` Bjorn Helgaas
2023-04-04 11:02           ` Xinghui Li
2023-04-17  9:15             ` Xinghui Li
2023-04-17 21:44               ` Bjorn Helgaas [this message]
2023-04-18  3:40                 ` 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=20230417214459.GA53460@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.