qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Cc: Halil Pasic <pasic@linux.vnet.ibm.com>,
	Pierre Morel <pmorel@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 5/5] s390x/css: support ccw IDA
Date: Thu, 21 Sep 2017 09:31:18 +0200	[thread overview]
Message-ID: <20170921093118.677e0819.cohuck@redhat.com> (raw)
In-Reply-To: <20170921005036.GL11080@bjsdjshi@linux.vnet.ibm.com>

On Thu, 21 Sep 2017 08:50:36 +0800
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> wrote:

> * Halil Pasic <pasic@linux.vnet.ibm.com> [2017-09-20 18:46:57 +0200]:

> > Thinking about this some more. Since in case of IDA we are guaranteed
> > to never cross a block boundary with a single IDAW we won't ever cross
> > block boundary. So we can do the check in ida_read_next_idaw by checking
> > bit 0x80000000 on the ccw->cda. So we could keep idaw_fmt2 and ccw_fmt1
> > local to ida_read_next_idaw and save one goto err. I think that would
> > look a bit nicer than what I have here in v3. Agree?  
> Agree. That would also do the check in the first place. Sounds better.

Can't argue with nicer code, either :) Looking forward to the next
version.

  reply	other threads:[~2017-09-21  7:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 18:27 [Qemu-devel] [PATCH v3 0/5] add CCW indirect data access support Halil Pasic
2017-09-19 18:27 ` [Qemu-devel] [PATCH v3 1/5] s390x/css: introduce css data stream Halil Pasic
2017-09-20  6:44   ` Dong Jia Shi
2017-09-19 18:27 ` [Qemu-devel] [PATCH v3 2/5] s390x/css: use ccw " Halil Pasic
2017-09-21  9:40   ` Pierre Morel
2017-09-19 18:27 ` [Qemu-devel] [PATCH v3 3/5] virtio-ccw: " Halil Pasic
2017-09-20  6:47   ` Dong Jia Shi
2017-09-20  7:58   ` Cornelia Huck
2017-09-20 10:56     ` Halil Pasic
2017-09-20 10:57       ` Cornelia Huck
2017-09-21  9:44   ` Pierre Morel
2017-09-21 17:01     ` Halil Pasic
2017-09-19 18:27 ` [Qemu-devel] [PATCH v3 4/5] 390x/css: introduce maximum data address checking Halil Pasic
2017-09-20  7:47   ` Dong Jia Shi
2017-09-20  8:25     ` Cornelia Huck
2017-09-20 11:02       ` Halil Pasic
2017-09-21  0:39         ` Dong Jia Shi
2017-09-20  8:06   ` Cornelia Huck
2017-09-20 11:34     ` Halil Pasic
2017-09-20 11:43       ` Cornelia Huck
2017-09-19 18:27 ` [Qemu-devel] [PATCH v3 5/5] s390x/css: support ccw IDA Halil Pasic
2017-09-20  7:42   ` Dong Jia Shi
2017-09-20  8:33     ` Cornelia Huck
2017-09-20 11:13       ` Halil Pasic
2017-09-20 11:18         ` Cornelia Huck
2017-09-20 16:46           ` Halil Pasic
2017-09-21  0:50             ` Dong Jia Shi
2017-09-21  7:31               ` Cornelia Huck [this message]
2017-09-21  1:10         ` Dong Jia Shi
2017-09-20  8:11   ` Cornelia Huck
2017-09-20 11:01     ` 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=20170921093118.677e0819.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=bjsdjshi@linux.vnet.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=pmorel@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 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).