All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Roman Kagan <rkagan@virtuozzo.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	Evgeny Yakovlev <eyakovlev@virtuozzo.com>,
	"Denis V . Lunev" <den@openvz.org>
Subject: Re: [PATCH kvm-unit-tests 5/5] add hyperv_connections test
Date: Tue, 13 Jun 2017 21:28:59 +0200	[thread overview]
Message-ID: <20170613192858.GB1276@potion> (raw)
In-Reply-To: <20170606191959.16987-6-rkagan@virtuozzo.com>

2017-06-06 22:19+0300, Roman Kagan:
> Add a test for Hyper-V message and event connections.
> 
> It requires QEMU with the extended test device supporting message end
> event connection test modes (recently posted on qemu-devel).  On older
> QEMU versions it fails.

Doesn't QEMU provide a way to detect this feature from the outside (some
command line magic) that we could use it to skip the test?

Thanks.

  reply	other threads:[~2017-06-13 19:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 19:19 [PATCH kvm-unit-tests 0/5] add test for hyperv connections Roman Kagan
2017-06-06 19:19 ` [PATCH kvm-unit-tests 1/5] hyperv: move test dev control codes to C file Roman Kagan
2017-06-06 19:19 ` [PATCH kvm-unit-tests 2/5] hyperv: don't take vcpu where inappropriate Roman Kagan
2017-06-06 19:19 ` [PATCH kvm-unit-tests 3/5] hyperv: add more test control codes Roman Kagan
2017-06-06 19:19 ` [PATCH kvm-unit-tests 4/5] hyperv: add more hyperv definitions Roman Kagan
2017-06-06 19:19 ` [PATCH kvm-unit-tests 5/5] add hyperv_connections test Roman Kagan
2017-06-13 19:28   ` Radim Krčmář [this message]
2017-06-14 11:28     ` Paolo Bonzini
2017-06-14 12:02       ` Roman Kagan
2017-06-14 12:01     ` Roman Kagan
2017-06-14 12:59       ` Radim Krčmář
2017-06-14 13:21         ` Roman Kagan
2017-06-14 16:34           ` Radim Krčmář
2017-06-14 18:58 ` [PATCH kvm-unit-tests 0/5] add test for hyperv connections Radim Krčmář

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=20170613192858.GB1276@potion \
    --to=rkrcmar@redhat.com \
    --cc=den@openvz.org \
    --cc=eyakovlev@virtuozzo.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkagan@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.