All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Markus Armbruster" <armbru@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
	peter.crosthwaite@xilinx.com, stefanha@redhat.com,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] IDs in QOM
Date: Thu, 02 Oct 2014 19:41:16 +0200	[thread overview]
Message-ID: <542D8E3C.6000207@redhat.com> (raw)
In-Reply-To: <87tx3ma56u.fsf@blackfin.pond.sub.org>

Il 02/10/2014 16:59, Markus Armbruster ha scritto:
> Andreas Färber <afaerber@suse.de> writes:
> 
>> Am 02.10.2014 um 16:21 schrieb Markus Armbruster:
>>> Andreas Färber <afaerber@suse.de> writes:
>>>
>>>> Am 02.10.2014 um 15:21 schrieb Stefan Hajnoczi:
>>>>> On Wed, Oct 01, 2014 at 02:33:47PM +0200, Markus Armbruster wrote:
>>>>>> Markus Armbruster <armbru@redhat.com> writes:
>>>>>
>>>>> This discussion seems orthogonal to your patch.  But I'm not applying it
>>>>> yet to give more time for discussion/review of the patch.
>>>>>
>>>>>> Is mangling array-ness into the name really a good idea?  Isn't this
>>>>>> type matter, not name matter?
>>>>>
>>>>> I agree.  It's nasty to hack the array selector into the name and will
>>>>> probably cause us pain down the line.
>>>
>>> Andreas?
>>
>> -> Paolo ;)
> 
> Paolo?

Uhm, I had written an answer but Thunderbird ate it.  Oh well.

I think foo[*] is not really a matter of typing, but a matter of
grouping similar children.  It does not really matter if foo[1] is
deleted while foo[2] still exists, and it does not really matter if the
next object created will be foo[1] or foo[3].

While we do not have any example, QOM could support true array
properties, e.g. with type intList.

Also note that while foo[*] was a generalization of MemoryRegion code,
the same idea has also existed forever for devices.
/machine/peripheral_anon and /machine/unattached do not currently use
automatic array-ification via foo[*], but they could.

>> If you just want to call id_wellformed() for -object / object-add, I
>> won't object to restricting it beyond the necessary, but it'll lead to
>> two places doing validity checks for QOM.
> 
> id_wellformed() is *already* called for -object and HMP object-add.
> That's exactly my point!
> 
> Please reread my explanation, and if it's insufficient, ask for
> clarification.
> 
> Subject: IDs in QOM (was: [PATCH] util: Emancipate id_wellformed() from QemuOpts)
> Date: Wed, 01 Oct 2014 14:33:47 +0200
> Message-ID: <87iok46kb8.fsf@blackfin.pond.sub.org>

I think it is okay to keep calling id_wellformed(), since it covers the
QOM-specific constraint that slashes must be outlawed.  It just makes
the children of /objects a bit more restricted in their naming, but that
is harmless because object_del can only delete objects created with
object_add.

Paolo

  reply	other threads:[~2014-10-02 17:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 11:59 [Qemu-devel] [PATCH] util: Emancipate id_wellformed() from QemuOpts Markus Armbruster
2014-09-30 15:30 ` Eric Blake
2014-10-01 12:33 ` [Qemu-devel] IDs in QOM (was: [PATCH] util: Emancipate id_wellformed() from QemuOpts) Markus Armbruster
2014-10-02 13:21   ` Stefan Hajnoczi
2014-10-02 13:26     ` [Qemu-devel] IDs in QOM Andreas Färber
2014-10-02 14:10       ` Stefan Hajnoczi
2014-10-02 14:21       ` Markus Armbruster
2014-10-02 14:28         ` Andreas Färber
2014-10-02 14:59           ` Markus Armbruster
2014-10-02 17:41             ` Paolo Bonzini [this message]
2014-10-07  8:01               ` Markus Armbruster
2014-10-07 10:03                 ` Paolo Bonzini
2014-10-07 12:16                   ` Markus Armbruster
2014-10-07 15:14                     ` Paolo Bonzini
2014-10-07 18:39                       ` Markus Armbruster
2014-10-07 18:42                         ` Paolo Bonzini
2014-10-07 18:41                       ` Kevin Wolf
2014-10-07 18:45                         ` Paolo Bonzini
2014-10-02 13:18 ` [Qemu-devel] [PATCH] util: Emancipate id_wellformed() from QemuOpts Stefan Hajnoczi
2014-10-02 13:42   ` Markus Armbruster
2014-10-02 14:11     ` Stefan Hajnoczi
2014-10-03  8:46 ` 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=542D8E3C.6000207@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.