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: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
	Pierre Morel <pmorel@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 4/5] 390x/css: introduce maximum data address checking
Date: Wed, 20 Sep 2017 13:43:58 +0200	[thread overview]
Message-ID: <20170920134358.568404ac.cohuck@redhat.com> (raw)
In-Reply-To: <1f526c43-6967-e30c-25c7-3b079e0598d3@linux.vnet.ibm.com>

On Wed, 20 Sep 2017 13:34:21 +0200
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:

> On 09/20/2017 10:06 AM, Cornelia Huck wrote:
> > On Tue, 19 Sep 2017 20:27:44 +0200
> > Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
> >   
> >> The architecture mandates the addresses to be  accessed on the first
> >> indirection level (that is, the data addresses without IDA, and the
> >> (M)IDAW addresses with (M)IDA) to be checked against an CCW format
> >> dependent limit maximum address.  If a violation is detected, the storage
> >> access is not to be performed and a channel program check needs to be
> >> generated. As of today, we fail to do this check.
> >>
> >> Let us stick even closer to the architecture specification.
> >>
> >> Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
> >> ---
> >>  hw/s390x/css.c         | 10 ++++++++++
> >>  include/hw/s390x/css.h |  1 +
> >>  2 files changed, 11 insertions(+)
> >>
> >> diff --git a/hw/s390x/css.c b/hw/s390x/css.c
> >> index 6b0cd8861b..2d37a9ddde 100644
> >> --- a/hw/s390x/css.c
> >> +++ b/hw/s390x/css.c
> >> @@ -795,6 +795,11 @@ static inline int cds_check_len(CcwDataStream *cds, int len)
> >>      return cds->flags & CDS_F_STREAM_BROKEN ? -EINVAL : len;
> >>  }
> >>  
> >> +static inline bool cds_ccw_addrs_ok(hwaddr addr, int len, bool ccw_fmt1)  
> > 
> > cds_cda_limit_ok?
> >   
> 
> I use cda to point to the 2 level in case of IDA. This is about
> level 1 (addressed by the ccw directly). That's why I used ccw_addrs
> but if you think cds_cda_limit_ok is better I can live with that.

I don't care that much, tbh.

> 
> We could also think about renaming cds->cda. Btw what does cda stand
> for (channel data address is my guess)?

Yes, cda should stand for 'channel data address'. Its usage in cds->cda
is probably the source of this minor confusion.

But, as said, I don't really care that much; so unless one of the other
folks has a strong opinion, feel free to leave as-is.

  reply	other threads:[~2017-09-20 14:11 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 [this message]
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
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=20170920134358.568404ac.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 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.