From: Thomas Gleixner <tglx@linutronix.de>
To: Jason Gunthorpe <jgg@ziepe.ca>, Shannon Nelson <shannon.nelson@amd.com>
Cc: alex.williamson@redhat.com, kevin.tian@intel.com,
reinette.chatre@intel.com, kvm@vger.kernel.org,
brett.creeley@amd.com, linux-kernel@vger.kernel.org,
Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [PATCH vfio] vfio/pci: remove msi domain on msi disable
Date: Mon, 18 Sep 2023 20:43:21 +0200 [thread overview]
Message-ID: <87led3xqye.ffs@tglx> (raw)
In-Reply-To: <20230918141705.GE13795@ziepe.ca>
On Mon, Sep 18 2023 at 11:17, Jason Gunthorpe wrote:
> On Thu, Sep 14, 2023 at 12:14:06PM -0700, Shannon Nelson wrote:
>> The new MSI dynamic allocation machinery is great for making the irq
>> management more flexible. It includes caching information about the
>> MSI domain which gets reused on each new open of a VFIO fd. However,
>> this causes an issue when the underlying hardware has flexible MSI-x
>> configurations, as a changed configuration doesn't get seen between
>> new opens, and is only refreshed between PCI unbind/bind cycles.
>>
>> In our device we can change the per-VF MSI-x resource allocation
>> without the need for rebooting or function reset. For example,
>>
>> 1. Initial power up and kernel boot:
>> # lspci -s 2e:00.1 -vv | grep MSI-X
>> Capabilities: [a0] MSI-X: Enable+ Count=8 Masked-
>>
>> 2. Device VF configuration change happens with no reset
>
> Is this an out of tree driver problem?
>
> The intree way to alter the MSI configuration is via
> sriov_set_msix_vec_count, and there is only one in-tree driver that
> uses it right now.
Right, but that only addresses the driver specific issues.
> If something is going wrong here it should be fixed in the
> sriov_set_msix_vec_count() machinery, possibly in the pci core to
> synchronize the msi_domain view of the world.
Right, we should definitely not do that on a per driver basis.
Thanks,
tglx
next prev parent reply other threads:[~2023-09-18 18:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 19:14 [PATCH vfio] vfio/pci: remove msi domain on msi disable Shannon Nelson
2023-09-18 14:17 ` Jason Gunthorpe
2023-09-18 17:48 ` Nelson, Shannon
2023-09-18 23:32 ` Jason Gunthorpe
2023-09-19 0:13 ` Nelson, Shannon
2023-09-18 18:43 ` Thomas Gleixner [this message]
2023-09-18 23:37 ` Jason Gunthorpe
2023-09-18 23:47 ` Thomas Gleixner
2023-09-19 0:02 ` Jason Gunthorpe
2023-09-19 0:25 ` Thomas Gleixner
2023-09-19 0:32 ` Jason Gunthorpe
2023-09-19 0:57 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2023-09-15 7:38 kernel test robot
2023-09-15 14:22 kernel test robot
2023-09-28 1:52 ` Liu, Yujie
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=87led3xqye.ffs@tglx \
--to=tglx@linutronix.de \
--cc=alex.williamson@redhat.com \
--cc=brett.creeley@amd.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=shannon.nelson@amd.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.