From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-2?Q?Luk=E1=B9_Doktor?= <ldoktor@redhat.com>
Subject: Re: [KVM-autotest] virtio_console test
Date: Fri, 20 Aug 2010 16:12:51 +0200
Message-ID: <4C6E8D63.6080409@redhat.com>
References: <1282311612-3282-1-git-send-email-ldoktor@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
Cc: jzupka@redhat.com, autotest@test.kernel.org, kvm@vger.kernel.org,
	akong@redhat.com
To: Lukas Doktor <ldoktor@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:30754 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752092Ab0HTOM5 (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 20 Aug 2010 10:12:57 -0400
In-Reply-To: <1282311612-3282-1-git-send-email-ldoktor@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Dne 20.8.2010 15:40, Lukas Doktor napsal(a):
> Hi,
>
> This patch adds new test for virtio_console. It supports booth, serialport and console, virtio_console types and it contains three tests:
> 1) smoke
> 2) loopback
> 3) perf
>
>
> Before any tests are executed it starts the machine with required number of virtio_consoles. Than it allows user to run all three tests. Using the parameters user can control which tests are executed and what setting is used. All tests supports multiple run using ';' separated list of settings. Most of the settings are optional only. The mandatory ones are written in CAPITALS.
>
> ad1) virtio_console_smoke format:
> $VIRTIO_CONSOLE_TYPE:$custom_data
>
> It creates a loopback via $VIRTIO_CONSOLE_TYPE console and sends $custom_data. If the received data match the original test pass
>
> ad2) virtio_console_loopback format:
> $SOURCE_CONSOLE_TYPE@$buffer_length:$DESTINATION_CONSOLE1_TYPE@$buffer_length:...:$DESTINATION_CONSOLEx_TYPE@$buffer_length:$loopback_buffer_length
>
> Creates loopback between the $SOURCE_CONSOLE_TYPE console and all following $DESTINATION_CONSOLEn_TYPE consoles. Than it sends data by $buffer_length to the source port. The loopback resends the data by $loopback_buffer_length to all destination consoles. The test listens on the destination consoles and controls the received data.
>
> NOTE: in the debug mode you can see the send/received data's buffers in every second during the test.
>
> ad3) virtio_console_perf format:
> $VIRTIO_CONSOLE_TYPE@$buffer_size:$test_duration
>
> First it sends the prepared data in a loop over $VIRTIO_CONSOLE_TYPE console from host to guest. Guest only reads all the data and throw them away. This part runs $test_duration seconds.
> Second it does the same from guest to host.
>
> For booth runs it provides information of minimum/median/maximum throughput and guest/host average loads.
>
>
> Best regards,
> Lukas Doktor
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


Just a note about kernels:
serialport works great but console have big issues. Use kernels >= 
2.6.35 for testing.