From: Pierre Morel <pmorel@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>, Halil Pasic <pasic@linux.ibm.com>
Cc: qemu-devel@nongnu.org, frankja@linux.ibm.com, thuth@redhat.com,
qemu-s390x@nongnu.org, david@redhat.com
Subject: Re: [PATCH v1] s390x: kvm-unit-tests: a PONG device for Sub Channels tests
Date: Thu, 14 Nov 2019 18:42:35 +0100 [thread overview]
Message-ID: <2c10ed4f-2b9e-89e7-0e3e-704355523239@linux.ibm.com> (raw)
In-Reply-To: <20191114141915.6dd5b9c8.cohuck@redhat.com>
On 2019-11-14 14:19, Cornelia Huck wrote:
> On Thu, 14 Nov 2019 14:02:35 +0100
> Halil Pasic <pasic@linux.ibm.com> wrote:
>
>> On Thu, 14 Nov 2019 11:38:23 +0100
>> Cornelia Huck <cohuck@redhat.com> wrote:
>>
>>> On Wed, 13 Nov 2019 20:02:33 +0100
>>> Pierre Morel <pmorel@linux.ibm.com> wrote:
>>>
...snip...
>> We made some different design decisions, while aiming essentially for the
>> same. Maybe it's due to different scope, maybe not. For instance one
>> can't test IDA with PONG, I guess.
> Now that I saw this again, I also recall the discussion of comparing it
> with the "testdev" for pci/isa. Anybody knows if these are used by
> kvm-unit-tests?
Only by X.
Regards,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2019-11-14 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 19:02 [PATCH v1] s390x: kvm-unit-tests: a PONG device for Sub Channels tests Pierre Morel
2019-11-14 10:38 ` Cornelia Huck
2019-11-14 12:33 ` Thomas Huth
2019-11-14 17:17 ` Pierre Morel
2019-11-15 14:22 ` Thomas Huth
2019-11-15 15:23 ` Pierre Morel
2019-11-14 13:02 ` Halil Pasic
2019-11-14 13:19 ` Cornelia Huck
2019-11-14 13:42 ` Halil Pasic
2019-11-14 17:42 ` Pierre Morel [this message]
2019-11-15 10:35 ` Cornelia Huck
2019-11-15 15:15 ` Pierre Morel
2019-11-14 17:37 ` Pierre Morel
2019-11-14 17:11 ` Pierre Morel
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=2c10ed4f-2b9e-89e7-0e3e-704355523239@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@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).