[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251022175335.GF21554@ziepe.ca>
Date: Wed, 22 Oct 2025 14:53:35 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Vipin Sharma <vipinsh@...gle.com>
Cc: Lukas Wunner <lukas@...ner.de>, bhelgaas@...gle.com,
alex.williamson@...hat.com, pasha.tatashin@...een.com,
dmatlack@...gle.com, 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 15/21] PCI: Make PCI saved state and capability
structs public
On Mon, Oct 20, 2025 at 04:49:34PM -0700, Vipin Sharma wrote:
> May be serialization and deserialization logic can be put in PCI and
> that way it can stay in PCI?
This does seem better
vfio should call something and get back a token it can store.
Jason
Powered by blists - more mailing lists