From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Paolo Bonzini <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: Thu, 3 Apr 2014 16:33:02 +0300 [thread overview]
Message-ID: <20140403133302.GB17155@redhat.com> (raw)
In-Reply-To: <533D449C.30806@suse.de>
On Thu, Apr 03, 2014 at 01:23:08PM +0200, Andreas Färber wrote:
> Am 03.04.2014 13:16, schrieb Michael S. Tsirkin:
> > On Wed, Apr 02, 2014 at 05:15:59PM +0200, Paolo Bonzini wrote:
> >> Il 02/04/2014 17:15, Michael S. Tsirkin ha scritto:
> >>> Yes and I think this someone was you actually.
> >>> Can something similar be done for this test?
> >>>
> >>
> >> I think ivshmem depends on ioeventfd, doesn't it? So short of
> >> implementing ioeventfd for TCG, no.
> >>
> >> Paolo
> >
> > Okay so will make check just fail on a non kvm host?
>
> Yes, this test fails on FreeBSD for instance, therefore this is a
> non-polished RFC. I'm hoping for comments how to best make it not crash.
>
> Cheers,
> Andreas
Well we could work around this
- start machine with kvm or without if not supported
- query ioeventfd support
But maybe it's easier to implement eventfd APIs ...
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-04-03 13:32 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
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 [this message]
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=20140403133302.GB17155@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=cam@cs.ualberta.ca \
--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 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).