[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALzav=dmx9ykjujAN0EiM3FPE9dFVaX4oXk=3Er9frtzsUT+1A@mail.gmail.com>
Date: Fri, 31 Oct 2025 14:24:09 -0700
From: David Matlack <dmatlack@...gle.com>
To: Vipin Sharma <vipinsh@...gle.com>
Cc: bhelgaas@...gle.com, alex.williamson@...hat.com, pasha.tatashin@...een.com,
jgg@...pe.ca, graf@...zon.com, pratyush@...nel.org,
gregkh@...uxfoundation.org, chrisl@...nel.org, rppt@...nel.org,
skhawaja@...gle.com, parav@...dia.com, saeedm@...dia.com,
kevin.tian@...el.com, jrhilke@...gle.com, david@...hat.com,
jgowans@...zon.com, dwmw2@...radead.org, epetron@...zon.de,
junaids@...gle.com, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
kvm@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [RFC PATCH 05/21] vfio/pci: Register VFIO live update file
handler to Live Update Orchestrator
On Fri, Oct 17, 2025 at 5:07 PM Vipin Sharma <vipinsh@...gle.com> wrote:
> diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_pci_core.c
> static int __init vfio_pci_core_init(void)
> {
> /* Allocate shared config space permission data used by all devices */
> + vfio_pci_liveupdate_init();
> return vfio_pci_init_perm_bits();
The call to vfio_pci_liveupdate_init() should go before the comment
associated with vfio_pci_init_perm_bits().
> diff --git a/drivers/vfio/pci/vfio_pci_liveupdate.c b/drivers/vfio/pci/vfio_pci_liveupdate.c
> +static bool vfio_pci_liveupdate_can_preserve(struct liveupdate_file_handler *handler,
> + struct file *file)
> +{
> + return -EOPNOTSUPP;
can_preserve() returns a bool, so this should be "return false". But I
think we can just do the cdev fops check in this commit. It is a small
enough change.
> +static struct liveupdate_file_handler vfio_pci_luo_handler = {
> + .ops = &vfio_pci_luo_fops,
> + .compatible = "vfio-v1",
This should probably be something like "vfio-pci-v1"?
Powered by blists - more mailing lists