From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57043) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQevb-0002Ed-6a for qemu-devel@nongnu.org; Wed, 25 Feb 2015 11:35:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YQevU-0002I1-Kl for qemu-devel@nongnu.org; Wed, 25 Feb 2015 11:35:15 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39353) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQevU-00028K-DU for qemu-devel@nongnu.org; Wed, 25 Feb 2015 11:35:08 -0500 From: John Snow Date: Wed, 25 Feb 2015 11:34:55 -0500 Message-Id: <1424882098-10674-1-git-send-email-jsnow@redhat.com> Subject: [Qemu-devel] [RFC 0/3] qtest: base64 r/w and faster memset List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: marc.mari.barcelo@gmail.com, pbonzini@redhat.com, John Snow , afaerber@suse.de, stefanha@redhat.com Adds new qtest protocol commands for base64 reads and writes, as well as a proper command for memset instead of faking it via write. RFC: Should base64 be the default, and hex nibbles be the opt-in? Base64 hampers the debugability of smaller reads/writes for which base64 won't provide much line speed improvement. On the other hand, the more efficient encoding could benefit any tests that send more than a couple of bytes of data at a time. John Snow (3): qtest: allow arbitrarily long sends qtest: Add base64 encoded read/write qtest: add memset to qtest protocol qtest.c | 94 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-- tests/libqtest.c | 39 ++++++++++++++++++----- tests/libqtest.h | 49 +++++++++++++++++++++++++++++ 3 files changed, 173 insertions(+), 9 deletions(-) -- 1.9.3