From: Zhi Wang <zhi.wang.linux@gmail.com>
To: Emily Deng <Emily.Deng@amd.com>
Cc: <amd-gfx@lists.freedesktop.org>, <bhelgaas@google.com>,
<alex.williamson@redhat.com>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH] PCI: Add vf reset notification for pf
Date: Mon, 5 Feb 2024 14:22:07 +0200 [thread overview]
Message-ID: <20240205142207.0000685a.zhi.wang.linux@gmail.com> (raw)
In-Reply-To: <20240204061257.1408243-1-Emily.Deng@amd.com>
On Sun, 4 Feb 2024 14:12:57 +0800
Emily Deng <Emily.Deng@amd.com> wrote:
> When a vf has been reset, the pf wants to get notification to remove
> the vf out of schedule.
>
> Solution:
> Add the callback function in pci_driver sriov_vf_reset_notification.
> When vf reset happens, then call this callback function.
>
> Signed-off-by: Emily Deng <Emily.Deng@amd.com>
> ---
> drivers/pci/pci.c | 8 ++++++++
> include/linux/pci.h | 1 +
> 2 files changed, 9 insertions(+)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 60230da957e0..aca937b05531 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -4780,6 +4780,14 @@ EXPORT_SYMBOL_GPL(pcie_flr);
> */
> int pcie_reset_flr(struct pci_dev *dev, bool probe)
> {
> + struct pci_dev *pf_dev;
> +
> + if (dev->is_virtfn) {
> + pf_dev = dev->physfn;
> + if (pf_dev->driver->sriov_vf_reset_notification)
> +
> pf_dev->driver->sriov_vf_reset_notification(pf_dev, dev);
> + }
> +
> if (dev->dev_flags & PCI_DEV_FLAGS_NO_FLR_RESET)
> return -ENOTTY;
>
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index c69a2cc1f412..4fa31d9b0aa7 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -926,6 +926,7 @@ struct pci_driver {
> int (*sriov_configure)(struct pci_dev *dev, int num_vfs);
> /* On PF */ int (*sriov_set_msix_vec_count)(struct pci_dev *vf, int
> msix_vec_count); /* On PF */ u32 (*sriov_get_vf_total_msix)(struct
> pci_dev *pf);
> + void (*sriov_vf_reset_notification)(struct pci_dev *pf,
> struct pci_dev *vf); const struct pci_error_handlers *err_handler;
> const struct attribute_group **groups;
> const struct attribute_group **dev_groups;
Hi:
I would suggest you can provide a cover letter including a complete
picture that tells the background, detailed problem statement, the
solutions and plus the users. As this seems very like a generic change,
it needs a better justification to convince folks why this is the best
solution. Without a complete picture, the solution just looks like a
workaround.
Thanks,
Zhi.
prev parent reply other threads:[~2024-02-05 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 6:12 [PATCH] PCI: Add vf reset notification for pf Emily Deng
2024-02-04 7:08 ` Keith Busch
2024-02-04 11:20 ` Leon Romanovsky
2024-02-05 3:47 ` Deng, Emily
2024-02-05 11:28 ` Christian König
2024-02-05 12:22 ` Zhi Wang [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=20240205142207.0000685a.zhi.wang.linux@gmail.com \
--to=zhi.wang.linux@gmail.com \
--cc=Emily.Deng@amd.com \
--cc=alex.williamson@redhat.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bhelgaas@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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