From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
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 3/8] s390x: improve error handling for SSCH and RSCH
Date: Wed, 11 Oct 2017 11:53:45 +0800 [thread overview]
Message-ID: <20171011035345.GE5350@bjsdjshi@linux.vnet.ibm.com> (raw)
In-Reply-To: <e2f89019-2def-c0bc-960c-9c7d06de30ec@linux.vnet.ibm.com>
* Halil Pasic <pasic@linux.vnet.ibm.com> [2017-10-10 12:06:23 +0200]:
>
>
> On 10/10/2017 10:13 AM, Dong Jia Shi wrote:
> > * Halil Pasic <pasic@linux.vnet.ibm.com> [2017-10-04 17:41:39 +0200]:
> >
> > [...]
> >
> >> diff --git a/hw/s390x/css.c b/hw/s390x/css.c
> >> index 4f47dbc8b0..b2978c3bae 100644
> >> --- a/hw/s390x/css.c
> >> +++ b/hw/s390x/css.c
> >> @@ -1003,12 +1003,11 @@ static void sch_handle_start_func_virtual(SubchDev *sch)
> >>
> >> }
> >>
> >> -static int sch_handle_start_func_passthrough(SubchDev *sch)
> >> +static IOInstEnding sch_handle_start_func_passthrough(SubchDev *sch)
> >> {
> >>
> >> PMCW *p = &sch->curr_status.pmcw;
> >> SCSW *s = &sch->curr_status.scsw;
> >> - int ret;
> >>
> >> ORB *orb = &sch->orb;
> >> if (!(s->ctrl & SCSW_ACTL_SUSP)) {
> >> @@ -1022,31 +1021,11 @@ static int sch_handle_start_func_passthrough(SubchDev *sch)
> >> */
> >> if (!(orb->ctrl0 & ORB_CTRL0_MASK_PFCH) ||
> >> !(orb->ctrl0 & ORB_CTRL0_MASK_C64)) {
> >> - return -EINVAL;
> >> + sch_gen_unit_exception(sch);
> >> + css_inject_io_interrupt(sch);
> > Last cycle, we agreed to add some log here. Sth. like:
> > warn_report("vfio-ccw requires PFCH and C64 flags set...");
> >
> > I promised to do a fix for this piece of code. But since this patch
> > already fixed it, I guess what I have to do is to add the log only? Or
> > you would like to add it by yourself? ;)
> >
>
> I think I forgot this one. Should there be a v3 I could add this too.
> Otherwise I would not mind if you do it on top.
>
[...]
> >> @@ -1084,16 +1063,15 @@ int do_subchannel_work_passthrough(SubchDev *sch)
> >> /* TODO: Halt handling */
> >> sch_handle_halt_func(sch);
> >> } else if (s->ctrl & SCSW_FCTL_START_FUNC) {
> >> - ret = sch_handle_start_func_passthrough(sch);
> >> + return sch_handle_start_func_passthrough(sch);
> >> }
> >> -
> >> - return ret;
> >> + return (IOInstEnding){.cc = 0};
> >> }
> >>
> >> -static int do_subchannel_work(SubchDev *sch)
> >> +static IOInstEnding do_subchannel_work(SubchDev *sch)
> >> {
> >> if (!sch->do_subchannel_work) {
> >> - return -EINVAL;
> >> + return (IOInstEnding){.cc = 1};
> > This keeps the logic here as-is, so it is right.
> >
>
> Yep.
>
> > Anybody agrees that also adding an assert() here?
>
> With automated regression testing in place I'm for it, without
> I feel uncomfortable doing it myself. You could do this
> on top if you like.
Got it.
Marked. I will look back after this series.
[...]
>
> Except for the missing warning are you OK with the rest
> of the patch? I would like to re-claim your r-b (dropped
> because changes weren't just minor).
I replied to the patch thread - the main part looks good to me.
I will save my r-b for the next round. ;)
--
Dong Jia Shi
next prev parent reply other threads:[~2017-10-11 3:53 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
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 [this message]
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=20171011035345.GE5350@bjsdjshi@linux.vnet.ibm.com \
--to=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=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 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.