From: Thomas Huth <thuth@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Cc: Pierre Morel <pmorel@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/8] s390x/css: IO instr handler ending control
Date: Mon, 9 Oct 2017 10:20:20 +0200 [thread overview]
Message-ID: <d6d2d73d-65c9-7ae1-fd37-cb8e304781e7@redhat.com> (raw)
In-Reply-To: <20171004154144.88995-3-pasic@linux.vnet.ibm.com>
On 04.10.2017 17:41, Halil Pasic wrote:
> CSS code needs to tell the IO instruction handlers located in how should
located in how?
> the emulated instruction be ended. Currently this is done by returning
> generic (POSIX) error codes, and mapping them to outcomes like condition
> codes. This makes bugs easy to create and hard to recognise.
>
> As a preparation for moving a way form (mis)using generic error codes for
> flow control let us introduce a struct which tells the instruction
> handler function how to end the instruction, in a more straight-forward
> and less ambiguous way.
>
> Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
> ---
> include/hw/s390x/css.h | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/include/hw/s390x/css.h b/include/hw/s390x/css.h
> index 0653d3c9be..66916b6546 100644
> --- a/include/hw/s390x/css.h
> +++ b/include/hw/s390x/css.h
> @@ -75,6 +75,18 @@ typedef struct CMBE {
> uint32_t reserved[7];
> } QEMU_PACKED CMBE;
>
> +/* IO instructions conclude according this */
> +typedef struct IOInstEnding {
> + /*
> + * General semantic of cc codes of IO instructions is (brief):
> + * 0 -- produced expected result
> + * 1 -- status conditions were present or produced alternate result
> + * 2 -- ineffective, because busy with previously initiated function
> + * 3 -- ineffective, not operational
> + */
> + int cc;
> +} IOInstEnding;
Why do you need a struct for this? Do you plan to extend it later? If
so, I think you should mention that in the patch description. If not,
please use a named enum or a "typedef unsigned int IOInstEnding" instead.
Thomas
next prev parent reply other threads:[~2017-10-09 8:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 15:41 [Qemu-devel] [PATCH v2 0/8] improve error handling for IO instr Halil Pasic
2017-10-04 15:41 ` [Qemu-devel] [PATCH v2 1/8] s390x/css: be more consistent if broken beyond repair Halil Pasic
2017-10-09 7:49 ` Dong Jia Shi
2017-10-10 13:25 ` Cornelia Huck
2017-10-10 14:39 ` Halil Pasic
2017-10-04 15:41 ` [Qemu-devel] [PATCH v2 2/8] s390x/css: IO instr handler ending control Halil Pasic
2017-10-09 8:20 ` Thomas Huth [this message]
2017-10-09 10:54 ` Halil Pasic
2017-10-09 11:07 ` Thomas Huth
2017-10-09 15:00 ` Halil Pasic
2017-10-10 10:28 ` Thomas Huth
2017-10-10 11:39 ` Cornelia Huck
2017-10-10 11:48 ` Halil Pasic
2017-10-10 11:41 ` Halil Pasic
2017-10-12 6:58 ` Thomas Huth
2017-10-12 11:44 ` Halil Pasic
2017-10-17 11:10 ` Halil Pasic
2017-10-17 11:28 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2017-10-17 12:13 ` Cornelia Huck
2017-10-17 13:03 ` Halil Pasic
2017-10-09 11:09 ` [Qemu-devel] " Cornelia Huck
2017-10-09 15:19 ` Halil Pasic
2017-10-04 15:41 ` [Qemu-devel] [PATCH v2 3/8] s390x: improve error handling for SSCH and RSCH Halil Pasic
2017-10-10 8:13 ` Dong Jia Shi
2017-10-10 10:06 ` Halil Pasic
2017-10-11 3:53 ` Dong Jia Shi
2017-10-10 13:07 ` Cornelia Huck
2017-10-10 14:36 ` Halil Pasic
2017-10-12 12:06 ` Halil Pasic
2017-10-12 12:11 ` Cornelia Huck
2017-10-12 12:17 ` Halil Pasic
2017-10-11 3:47 ` Dong Jia Shi
2017-10-11 10:54 ` Halil Pasic
2017-10-12 5:44 ` Dong Jia Shi
2017-10-04 15:41 ` [Qemu-devel] [PATCH v2 4/8] s390x: refactor error handling for XSCH handler Halil Pasic
2017-10-04 15:41 ` [Qemu-devel] [PATCH v2 5/8] s390x: refactor error handling for CSCH handler Halil Pasic
2017-10-04 15:41 ` [Qemu-devel] [PATCH v2 6/8] s390x: refactor error handling for HSCH handler Halil Pasic
2017-10-04 15:41 ` [Qemu-devel] [PATCH v2 7/8] s390x: refactor error handling for MSCH handler Halil Pasic
2017-10-04 15:41 ` [Qemu-devel] [PATCH v2 8/8] s390x: factor out common ioinst handler logic Halil Pasic
2017-10-10 13:10 ` Cornelia Huck
2017-10-10 14:37 ` 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=d6d2d73d-65c9-7ae1-fd37-cb8e304781e7@redhat.com \
--to=thuth@redhat.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=cohuck@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.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).