[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/2] ccw interpretation AR compliance improvemen

From: Cornelia Huck
Subject: Re: [Qemu-devel] [PATCH 0/2] ccw interpretation AR compliance improvements
Date: Thu, 27 Jul 2017 15:40:05 +0200

On Thu, 27 Jul 2017 15:18:01 +0200
Halil Pasic <address@hidden> wrote:

> [Re-posting my previous reply because I've accidentally
> dropped almost all addresses.]
> On 07/27/2017 10:26 AM, Cornelia Huck wrote:
> > On Wed, 26 Jul 2017 00:44:40 +0200
> > Halil Pasic <address@hidden> wrote:

> >> Regarding testing: did not do much more than a simple smoke test
> >> with virtio-ccw.  
> > 
> > I think we need a way to throw random channel programs at a channel
> > device...
> >   
> By random do you mean random random, or do you mean carefully crafted
> to provoke (and verify) certain responses. If it's more like the second
> case I've actually wrote something (a kernel driver) for 'internal use'
> but at the moment it's limited to indirect data access support (no test
> cases for invalid invalid channel programs).

That's what I've been thinking of. Standalone guest code would be even
better (can be integrated into automatic testing), but it's certainly

> The 'internal guys' say it
> probably ain't interesting for the rest of the world make this external,
> but if you are interested I could send you the patch these days.

Would be great if you could make this available. It is especially
interesting for me, but possibly for other folks working on s390 as well.

Might be good together with an "eat this" channel device in qemu.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]