[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251015163458.GI3938986@ziepe.ca>
Date: Wed, 15 Oct 2025 13:34:58 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: James Bottomley <James.Bottomley@...senpartnership.com>
Cc: Greg KH <gregkh@...uxfoundation.org>,
"Aneesh Kumar K.V" <aneesh.kumar@...nel.org>,
Jeremy Linton <jeremy.linton@....com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Dan Williams <dan.j.williams@...el.com>, linux-coco@...ts.linux.dev,
kvmarm@...ts.linux.dev, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, aik@....com, lukas@...ner.de,
Samuel Ortiz <sameo@...osinc.com>,
Xu Yilun <yilun.xu@...ux.intel.com>,
Suzuki K Poulose <Suzuki.Poulose@....com>,
Steven Price <steven.price@....com>,
Catalin Marinas <catalin.marinas@....com>,
Marc Zyngier <maz@...nel.org>, Will Deacon <will@...nel.org>,
Oliver Upton <oliver.upton@...ux.dev>
Subject: Re: [RFC PATCH v1 11/38] KVM: arm64: CCA: register host tsm platform
device
On Wed, Oct 15, 2025 at 11:19:41AM -0400, James Bottomley wrote:
> This came up for the SVSM as well: we want to expose things that can be
> virtual devices or other resources that the guest discovers. Our
> conclusion was we either needed to share one of the virtual busses
> (like virtio) or do our own svsm bus. The agreement was to implement
> our own bus, but we still haven't got around to it.
I think your own bus only makes sense if there is a structured
general discovery mechanism that can be used to automatically
enumerate the devices to create.
If you are open coding all the discovery via C tests in Linux then aux
bus is probably appropriate..
Jason
Powered by blists - more mailing lists