From: John Snow <jsnow@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: marc.mari.barcelo@gmail.com, afaerber@suse.de, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 4/4] libqos/ahci: Swap memread/write with bufread/write
Date: Tue, 05 May 2015 12:26:50 -0400 [thread overview]
Message-ID: <5548EF4A.4020002@redhat.com> (raw)
In-Reply-To: <5548EDAD.1030608@redhat.com>
On 05/05/2015 12:19 PM, Paolo Bonzini wrote:
>
>
> On 05/05/2015 17:48, John Snow wrote:
>> I specifically left things that alter control flow using hex nibbles --
>> such as the FIS packets, PRD tables, and all other existing tests. I
>> only use the b64 encoding for raw data patterns, which don't really need
>> to be debugged. Either they match or they don't: any particular values
>> are uninteresting.
>
> To some extent: they may still be interesting for stuff like IDENTIFY.
>
You got me there.
>> Any future test can be switched to/from hex/b64 by just altering
>> "mem{read,write}()" to "buf{read,write}()" as desired. I specifically
>> opted not to alter *all* qtest IO for this very reason.
>>
>> Does that help? :)
>
> Yes. We could also switch unconditionally to b64, but keep hex in the
> qtest-log.
>
Hmm, there's a thought. Though b64 for a handful of bytes seems
definitely likely to be slower. I am comfortable having two
implementations at the moment.
(Mostly because I don't feel like testing what the threshold for which
strings should be sent with what method is. Too much effort for qtest.)
hex-always in the log is a good idea, though. I may do that.
>> If you're not opposed to the rest of this series, I will send a v2
>> including the hex batching optimization.
>
> This series is okay. I just wanted some clarifications and ideas for
> future work.
>
> Paolo
>
Just trying to make you happy ;)
--js
prev parent reply other threads:[~2015-05-05 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 19:55 [Qemu-devel] [PATCH v2 0/4] qtest: base64 r/w and faster memset John Snow
2015-05-01 19:55 ` [Qemu-devel] [PATCH v2 1/4] qtest: allow arbitrarily long sends John Snow
2015-05-01 19:55 ` [Qemu-devel] [PATCH v2 2/4] qtest: Add base64 encoded read/write John Snow
2015-05-01 19:55 ` [Qemu-devel] [PATCH v2 3/4] qtest: add memset to qtest protocol John Snow
2015-05-01 19:55 ` [Qemu-devel] [PATCH v2 4/4] libqos/ahci: Swap memread/write with bufread/write John Snow
2015-05-01 20:48 ` Paolo Bonzini
2015-05-01 21:04 ` John Snow
2015-05-02 0:13 ` John Snow
2015-05-05 10:35 ` Paolo Bonzini
2015-05-05 15:48 ` John Snow
2015-05-05 16:19 ` Paolo Bonzini
2015-05-05 16:26 ` John Snow [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=5548EF4A.4020002@redhat.com \
--to=jsnow@redhat.com \
--cc=afaerber@suse.de \
--cc=marc.mari.barcelo@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).