From: Jeff Cody <jcody@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, berto@igalia.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, programmingkidx@gmail.com,
jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/4] util - add automated ID generation utility
Date: Tue, 13 Oct 2015 07:17:26 -0400 [thread overview]
Message-ID: <20151013111726.GA10945@localhost.localdomain> (raw)
In-Reply-To: <87ziznfccm.fsf@blackfin.pond.sub.org>
On Tue, Oct 13, 2015 at 09:37:29AM +0200, Markus Armbruster wrote:
> Jeff Cody <jcody@redhat.com> writes:
>
> > Multiple sub-systems in QEMU may find it useful to generate IDs
> > for objects that a user may reference via QMP or HMP. This patch
> > presents a standardized way to do it, so that automatic ID generation
> > follows the same rules.
> >
> > This patch enforces the following rules when generating an ID:
> >
> > 1.) Guarantee no collisions with a user-specified ID
> > 2.) Identify the sub-system the ID belongs to
> > 3.) Guarantee of uniqueness
> > 4.) Spoiling predictability, to avoid creating an assumption
> > of object ordering and parsing (i.e., we don't want users to think
> > they can guess the next ID based on prior behavior).
> >
> > The scheme for this is as follows (no spaces):
> >
> > # subsys D RR
> > Reserved char --| | | |
> > Subsystem String ----| | |
> > Unique number (64-bit) --| |
> > Two-digit random number ---|
> >
> > For example, a generated node-name for the block sub-system may look
> > like this:
> >
> > #block076
> >
> > The caller of id_generate() is responsible for freeing the generated
> > node name string with g_free().
> >
> > Reviewed-by: John Snow <jsnow@redhat.com>
> > Reviewed-by: Eric Blake <eblake@redhat.com>
> > Reviewed-by: Alberto Garcia <berto@igalia.com>
> > Signed-off-by: Jeff Cody <jcody@redhat.com>
> > ---
> > include/qemu-common.h | 8 ++++++++
> > util/id.c | 37 +++++++++++++++++++++++++++++++++++++
> > 2 files changed, 45 insertions(+)
> >
> > diff --git a/include/qemu-common.h b/include/qemu-common.h
> > index 0bd212b..2f74540 100644
> > --- a/include/qemu-common.h
> > +++ b/include/qemu-common.h
> > @@ -246,6 +246,14 @@ int64_t qemu_strtosz_suffix_unit(const char *nptr, char **end,
> > #define STR_OR_NULL(str) ((str) ? (str) : "null")
> >
> > /* id.c */
> > +
> > +typedef enum IdSubSystems {
> > + ID_QDEV,
>
> ID_QDEV is not used in this series. Do you intend to use it in a
> followup-series? Can we reasonably expect that series will be accepted?
>
John Arbuckle has a patch on list that uses it. I haven't reviewed
it, however - but I guess it depends ultimately on whether qdev will
allow autogeneration for its IDs or not.
> You could sidestep these questions by making id_generate() take a string
> argument ;)
>
I'd rather avoid having each system specifying a string inline in
their code. It is cleaner to have the strings defined in a central
location, I think (not to mention, easier to reference).
> > + ID_BLOCK,
> > + ID_MAX /* last element, used as array size */
> > +} IdSubSystems;
> > +
> > +char *id_generate(IdSubSystems id);
> > bool id_wellformed(const char *id);
> >
> > /* path.c */
> [...]
next prev parent reply other threads:[~2015-10-13 11:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 23:36 [Qemu-devel] [PATCH v3 0/4] Jeff Cody
2015-10-12 23:36 ` [Qemu-devel] [PATCH v3 1/4] util - add automated ID generation utility Jeff Cody
2015-10-13 7:37 ` Markus Armbruster
2015-10-13 11:17 ` Jeff Cody [this message]
2015-10-13 15:26 ` Markus Armbruster
2015-10-13 16:40 ` John Snow
2015-10-13 19:25 ` Programmingkid
2015-10-12 23:36 ` [Qemu-devel] [PATCH v3 2/4] block: auto-generated node-names Jeff Cody
2015-10-13 7:39 ` Markus Armbruster
2015-10-12 23:36 ` [Qemu-devel] [PATCH v3 3/4] block: add filter for generated node-names Jeff Cody
2015-10-12 23:36 ` [Qemu-devel] [PATCH v3 4/4] qemu-iotests: update tests " Jeff Cody
2015-10-13 7:41 ` Markus Armbruster
2015-10-13 11:18 ` Jeff Cody
2015-10-13 13:03 ` [Qemu-devel] [PATCH v3 0/4] Kevin Wolf
2015-10-13 15:26 ` Markus Armbruster
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=20151013111726.GA10945@localhost.localdomain \
--to=jcody@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).