From: Luiz Capitulino <lcapitulino@redhat.com>
To: Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Hajnoczi <stefanha@linux.vnet.ibm.com>,
kvm@vger.kernel.org, Kiszka <jan.kiszka@siemens.com>,
Stefan@gnu.org, qemu-devel@nongnu.org,
maneesh@linux.vnet.ibm.com, ananth@linux.vnet.ibm.com,
Jan@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH 1/3] export tdb_hash()
Date: Wed, 9 Jun 2010 17:35:06 -0300 [thread overview]
Message-ID: <20100609173506.454225c7@redhat.com> (raw)
In-Reply-To: <20100608123138.353f46f3@zephyr>
On Tue, 8 Jun 2010 12:31:38 +0530
Prerna Saxena <prerna@linux.vnet.ibm.com> wrote:
> This exports tdb_hash() for use by tracing framework.
Suggest to rename it (eg. qemu_hash()) and move it to a better location, qdict
is not the best module to export such service.
>
> Signed-off-by: Prerna Saxena <prerna@linux.vnet.ibm.com>
> ---
> qdict.c | 2 +-
> qdict.h | 2 ++
> 2 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/qdict.c b/qdict.c
> index 175bc17..5261872 100644
> --- a/qdict.c
> +++ b/qdict.c
> @@ -56,7 +56,7 @@ QDict *qobject_to_qdict(const QObject *obj)
> * tdb_hash(): based on the hash agorithm from gdbm, via tdb
> * (from module-init-tools)
> */
> -static unsigned int tdb_hash(const char *name)
> +unsigned int tdb_hash(const char *name)
> {
> unsigned value; /* Used to compute the hash value. */
> unsigned i; /* Used to cycle through random values. */
> diff --git a/qdict.h b/qdict.h
> index 5e5902c..d221c18 100644
> --- a/qdict.h
> +++ b/qdict.h
> @@ -59,4 +59,6 @@ int64_t qdict_get_try_int(const QDict *qdict, const char *key,
> int64_t err_value);
> const char *qdict_get_try_str(const QDict *qdict, const char *key);
>
> +/* Export tdb_hash() for use by trace framework */
> +unsigned int tdb_hash(const char *name);
> #endif /* QDICT_H */
next prev parent reply other threads:[~2010-06-09 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 6:58 [Qemu-devel] [PATCH 0/3] Monitor commands for 'simple' trace backend Prerna Saxena
2010-06-08 7:01 ` [Qemu-devel] [PATCH 1/3] export tdb_hash() Prerna Saxena
2010-06-09 20:35 ` Luiz Capitulino [this message]
2010-06-11 10:32 ` Prerna Saxena
2010-06-08 7:04 ` [Qemu-devel] [PATCH 2/3] Monitor command 'trace' Prerna Saxena
2010-06-09 20:37 ` Luiz Capitulino
2010-06-11 10:46 ` Prerna Saxena
2010-06-08 7:08 ` [Qemu-devel] [PATCH 3/3] Toggle tracepoint state Prerna Saxena
2010-06-09 20:43 ` Luiz Capitulino
2010-06-11 10:57 ` Prerna Saxena
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=20100609173506.454225c7@redhat.com \
--to=lcapitulino@redhat.com \
--cc=Jan@us.ibm.com \
--cc=Stefan@gnu.org \
--cc=aliguori@us.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=maneesh@linux.vnet.ibm.com \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).