public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org, xudong.hao@intel.com,
	aliguori@us.ibm.com, paul@codesourcery.com
Subject: Re: [PATCH] device-assignment: Rework "name" of assigned pci device
Date: Fri, 02 Jul 2010 11:24:39 +0200	[thread overview]
Message-ID: <4C2DB057.3090305@redhat.com> (raw)
In-Reply-To: <m3iq4yqp9i.fsf@blackfin.pond.sub.org>

   Hi,

> As far as I can tell, "name" predates the qdev conversion, and was used
> just for error messages and such.

Yes, was already there when I touched the code the first time.

> It defaulted to "host".  When Gerd
> did the qdev conversion, he made "id" default to "name", then "host".
> See commit 6b5bbd04.
>
> Defaulting "id" that way was probably not such a good idea.  We
> generally don't make up qdev IDs, because that risks collision with
> user-specified IDs.
>
> Since we've broken compatibility already, I figure we could just as well
> stop defaulting "id" to "host".  When we need to identify the device to
> the user, use "id" if it exists, else its PCI address.

Agree, we should not make up defaults for 'id'.  I did that in a few 
places where some naming existed already to ease transition.  nics with 
name= used to get that as default id too.  But in the end it turned out 
it caused more trouble than it helped ...

cheers,
   Gerd


      reply	other threads:[~2010-07-02  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28  2:37 [PATCH] device-assignment: Rework "name" of assigned pci device Hidetoshi Seto
2010-06-29  5:28 ` Markus Armbruster
2010-06-29  7:33   ` Hidetoshi Seto
2010-06-30  6:53     ` Markus Armbruster
2010-06-30 10:05       ` Hidetoshi Seto
2010-07-02  8:08         ` Markus Armbruster
2010-07-02  9:24           ` Gerd Hoffmann [this message]

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=4C2DB057.3090305@redhat.com \
    --to=kraxel@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=xudong.hao@intel.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