From: Pierre Morel <pmorel@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Eric Farman <farman@linux.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC v2] s390/css: handle CCW_FLAG_SKIP
Date: Tue, 7 May 2019 11:08:13 +0200 [thread overview]
Message-ID: <ee335c4c-468a-3e70-fe7e-02d0d77ef9d1@linux.ibm.com> (raw)
In-Reply-To: <20190507081251.24307-1-cohuck@redhat.com>
On 07/05/2019 10:12, Cornelia Huck wrote:
> If a ccw has CCW_FLAG_SKIP set, and the command is of type
> read, read backwards, or sense, no data should be written
> to the guest for that command.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
>
> v1 -> v2: fixed checks for command type [Eric]
>
> Still only lightly tested (it boots); I don't think I have a tool
> generating channel programs with the skip flag handy.
>
> ---
> hw/s390x/css.c | 22 ++++++++++++++++++----
> include/hw/s390x/css.h | 1 +
> 2 files changed, 19 insertions(+), 4 deletions(-)
>
> diff --git a/hw/s390x/css.c b/hw/s390x/css.c
> index 8fc9e35ba5d3..080ac7e5bc0b 100644
> --- a/hw/s390x/css.c
> +++ b/hw/s390x/css.c
> @@ -830,8 +830,12 @@ static int ccw_dstream_rw_noflags(CcwDataStream *cds, void *buff, int len,
> if (op == CDS_OP_A) {
> goto incr;
> }
> - ret = address_space_rw(&address_space_memory, cds->cda,
> - MEMTXATTRS_UNSPECIFIED, buff, len, op);
> + if (!cds->do_skip) {
> + ret = address_space_rw(&address_space_memory, cds->cda,
> + MEMTXATTRS_UNSPECIFIED, buff, len, op);
> + } else {
> + ret = 0;
> + }
> if (ret != MEMTX_OK) {
> cds->flags |= CDS_F_STREAM_BROKEN;
> return -EINVAL;
> @@ -928,8 +932,13 @@ static int ccw_dstream_rw_ida(CcwDataStream *cds, void *buff, int len,
> do {
> iter_len = MIN(len, cont_left);
> if (op != CDS_OP_A) {
> - ret = address_space_rw(&address_space_memory, cds->cda,
> - MEMTXATTRS_UNSPECIFIED, buff, iter_len, op);
> + if (!cds->do_skip) {
> + ret = address_space_rw(&address_space_memory, cds->cda,
> + MEMTXATTRS_UNSPECIFIED, buff, iter_len,
> + op);
> + } else {
> + ret = 0;
> + }
> if (ret != MEMTX_OK) {
> /* assume inaccessible address */
> ret = -EINVAL; /* channel program check */
> @@ -968,6 +977,11 @@ void ccw_dstream_init(CcwDataStream *cds, CCW1 const *ccw, ORB const *orb)
>
> cds->count = ccw->count;
> cds->cda_orig = ccw->cda;
> + /* skip is only effective for read, read backwards, or sense commands */
> + cds->do_skip = (ccw->flags & CCW_FLAG_SKIP) &&
> + ((ccw->cmd_code & CCW_CMD_BASIC_SENSE) == CCW_CMD_BASIC_SENSE ||
> + (ccw->cmd_code & 0x02) == 0x02 /* read */ ||
> + (ccw->cmd_code & 0x0c) == 0x0c /* read backwards */);
I think you should use masks like
((code & 0x3) == 2) => READ
((code & 0xf) == 0xc) => READ BACKWARD
((code & 0xf) == 0x4) => SENSE
Regards,
Pierre
> ccw_dstream_rewind(cds);
> if (!(cds->flags & CDS_F_IDA)) {
> cds->op_handler = ccw_dstream_rw_noflags;
> diff --git a/include/hw/s390x/css.h b/include/hw/s390x/css.h
> index aae19c427229..7cc183ef4366 100644
> --- a/include/hw/s390x/css.h
> +++ b/include/hw/s390x/css.h
> @@ -97,6 +97,7 @@ typedef struct CcwDataStream {
> int (*op_handler)(struct CcwDataStream *cds, void *buff, int len,
> CcwDataStreamOp op);
> hwaddr cda;
> + bool do_skip;
> } CcwDataStream;
>
> /*
>
--
Pierre Morel
Linux/KVM/QEMU in Böblingen - Germany
next prev parent reply other threads:[~2019-05-07 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 8:12 [Qemu-devel] [PATCH RFC v2] s390/css: handle CCW_FLAG_SKIP Cornelia Huck
2019-05-07 9:08 ` Pierre Morel [this message]
2019-05-07 15:31 ` Eric Farman
2019-05-08 8:44 ` Cornelia Huck
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=ee335c4c-468a-3e70-fe7e-02d0d77ef9d1@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).