From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: thuth@redhat.com, frankja@linux.ibm.com, david@redhat.com,
qemu-devel@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
qemu-s390x@nongnu.org
Subject: Re: [PATCH v1] s390x: kvm-unit-tests: a PONG device for Sub Channels tests
Date: Fri, 15 Nov 2019 11:35:12 +0100 [thread overview]
Message-ID: <20191115113512.2b9be20e.cohuck@redhat.com> (raw)
In-Reply-To: <2c10ed4f-2b9e-89e7-0e3e-704355523239@linux.ibm.com>
On Thu, 14 Nov 2019 18:42:35 +0100
Pierre Morel <pmorel@linux.ibm.com> wrote:
> 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.
If they use it, it might make sense for s390 to use a comparable
approach.
Btw, I created https://wiki.qemu.org/Testing/CCWTestDevice back then;
might make sense to collect ideas there?
>
> Regards,
>
> Pierre
>
>
next prev parent reply other threads:[~2019-11-15 10:36 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
2019-11-15 10:35 ` Cornelia Huck [this message]
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=20191115113512.2b9be20e.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@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 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.