qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	"Jason J . Herne" <jjherne@linux.vnet.ibm.com>,
	Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 2/2] s390x/3270: handle writes of arbitrary length
Date: Thu, 21 Sep 2017 12:30:11 +0200	[thread overview]
Message-ID: <d36a9f7f-bbf1-0815-a0c1-c9f36cdd1803@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170921112341.59175a29.cohuck@redhat.com>



On 09/21/2017 11:23 AM, Cornelia Huck wrote:
> On Wed, 20 Sep 2017 19:23:14 +0200
> Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
> 
>> The problem is, that the current implementation places unrealistic and
>> arbitrary constraints on the length of writes to the device (that is the
>> outbound requests), by asserting ccw.count being such that that even the
>> worst case escaped payload will fit an  more or less arbitrary sized
>> buffer. Actually on protocol level there is nothing to justify such
>> a limitation.
>>
>> Another strange thing is the return value which more or less reflects
>> the size (written) after escaping instead of before escaping. This
>> is strange, because this return value is used to calculate SCSW.count.
> 
> Didn't the Linux driver care about the count?
> 

Maybe Jason can answer that. I did only most basic testing with my patch
applied (and basically no testing without my changes).

>From code perspective I'm sure it does for the reads. For the writes
I did not look into that.

Halil

>>
>> Let us teach 3270 how to deal with arbitrary long writes.
>>
>> Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
>> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> Reviewed-by: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
>> Reported-by: Jason J . Herne <jjherne@linux.vnet.ibm.com>
>> Tested-by: Jason J . Herne <jjherne@linux.vnet.ibm.com>
>> ---
>>  hw/char/terminal3270.c | 30 ++++++++++++++++++------------
>>  1 file changed, 18 insertions(+), 12 deletions(-)
> 
> Looks good.
> 

  reply	other threads:[~2017-09-21 10:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 17:23 [Qemu-devel] [PATCH 0/2] 3270 improvements Halil Pasic
2017-09-20 17:23 ` [Qemu-devel] [PATCH 1/2] s390x/3270: IDA support for 3270 via CcwDataStream Halil Pasic
2017-09-21  9:15   ` Cornelia Huck
2017-09-21 11:22     ` Halil Pasic
2017-09-21 12:05       ` Cornelia Huck
2017-09-21 16:11         ` Halil Pasic
2017-09-22 13:38           ` Cornelia Huck
2017-09-20 17:23 ` [Qemu-devel] [PATCH 2/2] s390x/3270: handle writes of arbitrary length Halil Pasic
2017-09-21  9:23   ` Cornelia Huck
2017-09-21 10:30     ` Halil Pasic [this message]
2017-09-20 18:22 ` [Qemu-devel] [PATCH 0/2] 3270 improvements no-reply
2017-09-21  9:24 ` Cornelia Huck
2017-09-21 10:22   ` Halil Pasic
2017-09-21 10:48     ` Cornelia Huck
2017-09-21 11:00       ` Halil Pasic
2017-09-27 14:15         ` Halil Pasic
2017-09-28 15:19 ` Cornelia Huck
2017-09-28 15:20   ` Halil Pasic

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=d36a9f7f-bbf1-0815-a0c1-c9f36cdd1803@linux.vnet.ibm.com \
    --to=pasic@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=bjsdjshi@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).