From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Pierre Morel <pmorel@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/8] s390x/css: be more consistent if broken beyond repair
Date: Tue, 10 Oct 2017 15:25:51 +0200 [thread overview]
Message-ID: <20171010152551.33ab63f3.cohuck@redhat.com> (raw)
In-Reply-To: <20171004154144.88995-2-pasic@linux.vnet.ibm.com>
On Wed, 4 Oct 2017 17:41:37 +0200
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
> Calling do_subchannel_work with no function control flags set in SCSW is
> a programming error. Currently the handle this differently in
> do_subchannel_work_virtual and do_subchannel_work_passthrough. Let's be
> consistent and guard with a common assert against this programming error.
>
> Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
> ---
> hw/s390x/css.c | 16 ++++------------
> 1 file changed, 4 insertions(+), 12 deletions(-)
Thanks, applied.
next prev parent reply other threads:[~2017-10-10 13:26 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 [this message]
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
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=20171010152551.33ab63f3.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 \
--cc=thuth@redhat.com \
/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).