All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: pbonzini@redhat.com, Cam Macdonell <cam@cs.ualberta.ca>,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [RFC] tests: Add ivshmem qtest
Date: Wed, 02 Apr 2014 17:07:09 +0200	[thread overview]
Message-ID: <533C279D.4090402@suse.de> (raw)
In-Reply-To: <20140402150605.GC11627@redhat.com>

Am 02.04.2014 17:06, schrieb Michael S. Tsirkin:
> On Wed, Apr 02, 2014 at 04:57:48PM +0200, Andreas Färber wrote:
>> Note that it launches two instances to as sharing memory is the purpose
>> of Nahanni/ivshmem.
>>
>> Cc: Cam Macdonell <cam@cs.ualberta.ca>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> ---
>>  This test demonstrates a use case of running two QEMU instances in qtest.
>>
>>  However, similar to mst's proposed KVM acpi-test, it fails on systems
>>  without KVM support,
> 
> Hmm, acpi-test no longer depends on kvm.

You only committed the TCG version due to someone raising the issue. But
maybe I'm mistaken...

Andreas

>> and we cannot use $(CONFIG_KVM) to make it conditional
>>  since that is a per-target define rather than host-wide.
>>
>>  I wonder if libqtest should expose an API to start a QEMU instance and
>>  inquire via QMP whether the executable supports KVM, returning true or false?

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-04-02 15:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 14:57 [Qemu-devel] [RFC] tests: Add ivshmem qtest Andreas Färber
2014-04-02 15:06 ` Michael S. Tsirkin
2014-04-02 15:07   ` Andreas Färber [this message]
2014-04-02 15:15     ` Michael S. Tsirkin
2014-04-02 15:15       ` Paolo Bonzini
2014-04-03 11:16         ` Michael S. Tsirkin
2014-04-03 11:23           ` Andreas Färber
2014-04-03 13:33             ` Michael S. Tsirkin
2014-04-03  8:46 ` Stefan Hajnoczi
2014-04-03 11:45   ` Andreas Färber
2014-04-03 12:58     ` Stefan Hajnoczi

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=533C279D.4090402@suse.de \
    --to=afaerber@suse.de \
    --cc=cam@cs.ualberta.ca \
    --cc=mst@redhat.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 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.