From: Stefan Hajnoczi <stefanha@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "John G Johnson" <john.g.johnson@oracle.com>,
mtsirkin@redhat.com, "Daniel P. Berrangé" <berrange@redhat.com>,
quintela@redhat.com, "Jason Wang" <jasowang@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Kirti Wankhede" <kwankhede@nvidia.com>,
"Thanos Makatos" <thanos.makatos@nutanix.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Felipe Franciosi" <felipe@nutanix.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: VFIO Migration
Date: Thu, 5 Nov 2020 11:42:17 +0000 [thread overview]
Message-ID: <20201105114217.GD462479@stefanha-x1.localdomain> (raw)
In-Reply-To: <20201105064724.qd55txohwbfpvdsg@sirius.home.kraxel.org>
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
On Thu, Nov 05, 2020 at 07:47:24AM +0100, Gerd Hoffmann wrote:
> > > > 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.
>
> I think both android and ios use that too, for app naming (but maybe that
> comes from java).
>
> > 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?
>
> Having "https://" at the start is odd, especially if we don't require
> that the given URL returns something useful. Other that that I don't
> mind that much whenever we use go-style or java-style strings, with a
> slight preference for the latter for consistency with virtio-serial.
Thanks for explaining. We can discuss the exact format in the next
revision if there are opinions.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-05 11:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 11:11 VFIO Migration Stefan Hajnoczi
2020-11-02 12:28 ` Cornelia Huck
2020-11-02 14:56 ` Stefan Hajnoczi
2020-11-04 8:07 ` Gerd Hoffmann
2020-11-04 16:40 ` Stefan Hajnoczi
2020-11-05 6:47 ` Gerd Hoffmann
2020-11-05 11:42 ` Stefan Hajnoczi [this message]
2020-11-02 19:38 ` Alex Williamson
2020-11-03 11:03 ` Stefan Hajnoczi
2020-11-03 17:13 ` Alex Williamson
2020-11-03 18:09 ` Stefan Hajnoczi
2020-11-05 23:37 ` Yan Zhao
2020-11-03 8:46 ` Jason Wang
2020-11-03 12:15 ` Stefan Hajnoczi
2020-11-04 3:32 ` Jason Wang
2020-11-04 7:16 ` Stefan Hajnoczi
2020-11-03 11:39 ` Daniel P. Berrangé
2020-11-03 15:05 ` Stefan Hajnoczi
2020-11-03 15:23 ` Daniel P. Berrangé
2020-11-03 18:16 ` Stefan Hajnoczi
2020-11-03 12:17 ` Dr. David Alan Gilbert
2020-11-03 15:27 ` Stefan Hajnoczi
2020-11-03 18:49 ` Dr. David Alan Gilbert
2020-11-04 7:36 ` Stefan Hajnoczi
2020-11-04 10:14 ` Dr. David Alan Gilbert
2020-11-04 16:47 ` Stefan Hajnoczi
2020-11-04 17:32 ` Dr. David Alan Gilbert
2020-11-05 11:40 ` Stefan Hajnoczi
2020-11-05 12:13 ` Dr. David Alan Gilbert
2020-11-05 12:47 ` Michael S. Tsirkin
2020-11-05 14:17 ` Dr. David Alan Gilbert
2020-11-05 12:53 ` Michael S. Tsirkin
2020-11-04 11:05 ` Christophe de Dinechin
2020-11-03 15:23 ` Christophe de Dinechin
2020-11-03 15:33 ` Daniel P. Berrangé
2020-11-03 17:31 ` Alex Williamson
2020-11-04 10:13 ` Stefan Hajnoczi
2020-11-04 11:10 ` Stefan Hajnoczi
2020-11-04 7:50 ` Michael S. Tsirkin
2020-11-04 16:37 ` Stefan Hajnoczi
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=20201105114217.GD462479@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=felipe@nutanix.com \
--cc=jasowang@redhat.com \
--cc=john.g.johnson@oracle.com \
--cc=kraxel@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=mtsirkin@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thanos.makatos@nutanix.com \
/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;
as well as URLs for NNTP newsgroup(s).