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: Wed, 20 Sep 2017 10:33:12 +0200 [thread overview]
Message-ID: <20170920103312.50b8b69b.cohuck@redhat.com> (raw)
In-Reply-To: <20170920074238.GH11080@bjsdjshi@linux.vnet.ibm.com>
On Wed, 20 Sep 2017 15:42:38 +0800
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> wrote:
> * Halil Pasic <pasic@linux.vnet.ibm.com> [2017-09-19 20:27:45 +0200]:
>
> > Let's add indirect data addressing support for our virtual channel
> > subsystem. This implementation does not bother with any kind of
> > prefetching. We simply step through the IDAL on demand.
> >
> > Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
> > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> > ---
> > hw/s390x/css.c | 117 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> > 1 file changed, 116 insertions(+), 1 deletion(-)
> >
> > diff --git a/hw/s390x/css.c b/hw/s390x/css.c
> > index 2d37a9ddde..a3ce6d89b6 100644
> > --- a/hw/s390x/css.c
> > +++ b/hw/s390x/css.c
> > @@ -827,6 +827,121 @@ incr:
> > return 0;
> > }
> >
> > +/* returns values between 1 and bsz, where bsz is a power of 2 */
> > +static inline uint16_t ida_continuous_left(hwaddr cda, uint64_t bsz)
> > +{
> > + return bsz - (cda & (bsz - 1));
> > +}
> > +
> > +static inline uint64_t ccw_ida_block_size(uint8_t flags)
> > +{
> > + if ((flags & CDS_F_C64) && !(flags & CDS_F_I2K)) {
> > + return 1ULL << 12;
> > + }
> > + return 1ULL << 11;
> > +}
> > +
> > +static inline int ida_read_next_idaw(CcwDataStream *cds, bool ccw_fmt1,
> > + bool idaw_fmt_2)
> > +{
> > + union {uint64_t fmt2; uint32_t fmt1; } idaw;
> > + int ret;
> > + hwaddr idaw_addr;
> > +
> > + if (idaw_fmt_2) {
> > + idaw_addr = cds->cda_orig + sizeof(idaw.fmt2) * cds->at_idaw;
> > + if (idaw_addr & 0x07 && cds_ccw_addrs_ok(idaw_addr, 0, ccw_fmt1)) {
> > + return -EINVAL; /* channel program check */
> > + }
> > + ret = address_space_rw(&address_space_memory, idaw_addr,
> Ahh, just got one question here:
> Do we need to considerate endianess for idaw_addr?
That is taken care of below.
And the previous version worked on my laptop via tcg ;)
>
> > + MEMTXATTRS_UNSPECIFIED, (void *) &idaw.fmt2,
> > + sizeof(idaw.fmt2), false);
> > + cds->cda = be64_to_cpu(idaw.fmt2);
> > + } else {
> > + idaw_addr = cds->cda_orig + sizeof(idaw.fmt1) * cds->at_idaw;
> > + if (idaw_addr & 0x03 && cds_ccw_addrs_ok(idaw_addr, 0, ccw_fmt1)) {
> > + return -EINVAL; /* channel program check */
> > + }
> > + ret = address_space_rw(&address_space_memory, idaw_addr,
> > + MEMTXATTRS_UNSPECIFIED, (void *) &idaw.fmt1,
> > + sizeof(idaw.fmt1), false);
> > + cds->cda = be64_to_cpu(idaw.fmt1);
> Still need to check bit 0x80000000 here I think.
Yes, I think this is 'must be zero' for format-1 idaws, and not covered
by the ccw-format specific checks above. (Although the PoP can be a bit
confusing with many similar terms...)
>
> > + }
> > + ++(cds->at_idaw);
> > + if (ret != MEMTX_OK) {
> > + /* assume inaccessible address */
> > + return -EINVAL; /* channel program check */
> > +
> Extra line.
>
> > + }
> > + return 0;
> > +}
> > +
> > +static int ccw_dstream_rw_ida(CcwDataStream *cds, void *buff, int len,
> > + CcwDataStreamOp op)
> > +{
> > + uint64_t bsz = ccw_ida_block_size(cds->flags);
> > + int ret = 0;
> > + uint16_t cont_left, iter_len;
> > + const bool idaw_fmt2 = cds->flags & CDS_F_C64;
> > + bool ccw_fmt1 = cds->flags & CDS_F_FMT;
> Use 'const bool' either? Although I doubt the value of using const here.
> ;)
Both being the same is still a good idea.
>
> > +
> > + ret = cds_check_len(cds, len);
> > + if (ret <= 0) {
> > + return ret;
> > + }
>
> [...]
>
next prev parent reply other threads:[~2017-09-20 13:24 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 [this message]
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=20170920103312.50b8b69b.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).