All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] ccw interpretation AR compliance improvements
Date: Thu, 27 Jul 2017 16:24:00 +0200	[thread overview]
Message-ID: <20170727162400.4a3fd483@gondolin> (raw)
In-Reply-To: <8f101d44-4d7d-9a13-8d0c-ebb830010847@linux.vnet.ibm.com>

On Thu, 27 Jul 2017 15:52:23 +0200
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:

> On 07/27/2017 03:40 PM, Cornelia Huck wrote:
> > On Thu, 27 Jul 2017 15:18:01 +0200
> > Halil Pasic <pasic@linux.vnet.ibm.com> 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 <pasic@linux.vnet.ibm.com> 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
> > useful.
> >   
> >> 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.  
> 
> It is very wip and I don't feel comfortable with sharing it
> with the world yet. But I'm definitely interested in making this
> available. I haven't figured out what would be the best way to make
> it available, and I hope you can help me with that.

Do you have a git tree somewhere you can dump it?

> 
> > 
> > Might be good together with an "eat this" channel device in qemu.
> >   
> 
> If course I do have a qemu counterpart.

And of course I'd love to see that as well :)

> 
> To sum it up, one I'm done with the next iteration I'm gonna send
> you with the patches unless you say otherwise.
> 
> Regards,
> Halil
> 

      reply	other threads:[~2017-07-27 14:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 22:44 [Qemu-devel] [PATCH 0/2] ccw interpretation AR compliance improvements Halil Pasic
2017-07-25 22:44 ` [Qemu-devel] [PATCH 1/2] s390x/css: check ccw address validity Halil Pasic
2017-07-26  3:31   ` Dong Jia Shi
2017-07-26 12:05     ` Halil Pasic
2017-07-26 16:45       ` Halil Pasic
2017-07-27  1:03         ` Dong Jia Shi
2017-07-25 22:44 ` [Qemu-devel] [PATCH 2/2] s390x/css: fix bits must be zero check for TIC Halil Pasic
2017-07-26  3:01   ` Dong Jia Shi
2017-07-26 11:38     ` Halil Pasic
2017-07-27  0:41       ` Dong Jia Shi
2017-07-27  8:01   ` Cornelia Huck
2017-07-27 11:18     ` Halil Pasic
2017-07-27 13:40     ` Halil Pasic
2017-07-27 13:45       ` Cornelia Huck
2017-07-27  8:32   ` Cornelia Huck
2017-07-27  8:43     ` Dong Jia Shi
2017-07-27  8:26 ` [Qemu-devel] [PATCH 0/2] ccw interpretation AR compliance improvements Cornelia Huck
2017-07-27 11:34   ` Halil Pasic
2017-07-27 13:18   ` Halil Pasic
2017-07-27 13:40     ` Cornelia Huck
2017-07-27 13:52       ` Halil Pasic
2017-07-27 14:24         ` Cornelia Huck [this message]

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=20170727162400.4a3fd483@gondolin \
    --to=cohuck@redhat.com \
    --cc=bjsdjshi@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /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.