kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: "Lukáš Doktor" <ldoktor@redhat.com>
Cc: jzupka@redhat.com, autotest@test.kernel.org, kvm@vger.kernel.org,
	akong@redhat.com
Subject: Re: [KVM-autotest] virtio_console test
Date: Mon, 23 Aug 2010 13:23:46 +0530	[thread overview]
Message-ID: <20100823075346.GG2721@amit-laptop.redhat.com> (raw)
In-Reply-To: <4C6E8D63.6080409@redhat.com>

On (Fri) Aug 20 2010 [16:12:51], Lukáš Doktor wrote:
> 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

This is great, thanks for the tests.

I was working with Lucas at the KVM Forum to get my virtio-console tests
integrated upstream. I have a few micro tests that test correctness of
various bits in the virtio_console code:

http://fedorapeople.org/gitweb?p=amitshah/public_git/test-virtserial.git

It would be great to sync up with Lucas and add those tests to autotest
as well.

Eventually, I'd also like to adapt the C code to python so that it
integrates with KVM-autotest.

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

Can you tell me what the issues are? I test console io in the testsuite
mentioned above and it's been passing fine.

		Amit

  reply	other threads:[~2010-08-23  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 13:40 [KVM-autotest] virtio_console test Lukas Doktor
2010-08-20 13:40 ` [PATCH] NEW " Lukas Doktor
2010-08-20 14:12 ` [KVM-autotest] " Lukáš Doktor
2010-08-23  7:53   ` Amit Shah [this message]
2010-08-23 13:20     ` Lukáš Doktor
2010-08-23 13:42       ` Amit Shah

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=20100823075346.GG2721@amit-laptop.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=akong@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=jzupka@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=ldoktor@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).