[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: VFIO Migration
From: |
Stefan Hajnoczi |
Subject: |
Re: VFIO Migration |
Date: |
Wed, 4 Nov 2020 16:40:10 +0000 |
On Wed, Nov 04, 2020 at 09:07:45AM +0100, Gerd Hoffmann wrote:
> > > > The hardware interface together with the device state representation is
> > > > called
> > > > a *device model*. Device models can be assigned URIs such as
> > > > https://qemu.org/devices/e1000e to uniquely identify them.
> > >
> > > Is that something that needs to be put together for every device where we
> > > want to support migration? How do you create the URI?
> >
> > Yes. If you are creating a custom device that no one else needs to
> > emulate then you can simply pick a unique URL:
> >
> > https://vendor.com/my-dev
> >
> > There doesn't need to be anything at the URL. It's just a unique string
> > that no one else will use and therefore web URLs are handy because no
> > one else will accidentally pick your string.
>
> If this is just a string I think it would be better to use the reverse
> domain name scheme (as used by virtio-serial too), i.e.
>
> - org.qemu.devices.e1000e
> - com.vendor.my-dev
This is the Java syntax. Go uses gitlab.com/my-user/foo and I think it's
nicer but I think I'm bikeshedding.
Is there any particular reason why you prefer the reverse domain name
approach?
Stefan
signature.asc
Description: PGP signature
Re: VFIO Migration, Alex Williamson, 2020/11/02
Re: VFIO Migration, Jason Wang, 2020/11/03