From: Jan Kiszka <jan.kiszka@siemens.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Registering buffers with a qdict
Date: Fri, 07 May 2010 16:21:13 +0200 [thread overview]
Message-ID: <4BE421D9.30502@siemens.com> (raw)
In-Reply-To: <20100507100758.1050a374@redhat.com>
Luiz Capitulino wrote:
> On Fri, 07 May 2010 13:45:03 +0200
> Jan Kiszka <jan.kiszka@siemens.com> wrote:
>
>> Hi Luiz,
>>
>> what is the recommended way of pushing larger buffers (up to 64K so far)
>> into a qdict? QLIST of QINT (one per byte) looks a bit heavy. I thought
>> about hex-encoding the content first (series of "%02X"), then
>> registering it as QSTRING. Or should we introduce a new type, QBUFFER?
>
> I don't think that hex-encoding the contents is so bad if your use case is
> very specific and isolated.
The focus will be first on visualizing the buffer (user_print), but who
knows what happens once the services is also exposed via QMP.
>
> On the other hand, I do prefer a QBuffer type, specially because we can
> have buffer operations.
The q<type>.c files look sufficiently simply, guess I will add a buffer
type. Still, hex-encoding is probably the best representation for QMP.
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-05-07 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 11:45 [Qemu-devel] Registering buffers with a qdict Jan Kiszka
2010-05-07 13:07 ` [Qemu-devel] " Luiz Capitulino
2010-05-07 14:21 ` Jan Kiszka [this message]
2010-05-07 16:59 ` Luiz Capitulino
2010-05-10 10:59 ` Jan Kiszka
2010-05-10 13:26 ` Luiz Capitulino
2010-05-10 13:28 ` Avi Kivity
2010-05-10 13:43 ` Jan Kiszka
2010-05-10 14:14 ` Avi Kivity
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=4BE421D9.30502@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=lcapitulino@redhat.com \
--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).