public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: Janosch Frank <frankja@linux.ibm.com>,
	linux-s390@vger.kernel.org, thuth@redhat.com,
	kvm@vger.kernel.org, david@redhat.com, nrb@linux.ibm.com,
	nsg@linux.ibm.com, cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH 1/1] s390x: sclp: consider monoprocessor on read_info error
Date: Tue, 25 Apr 2023 14:16:34 +0200	[thread overview]
Message-ID: <20230425141634.1e18b172@p-imbrenda> (raw)
In-Reply-To: <bc3cf8c5-1aa9-0db3-c212-9c09554d4ab2@linux.ibm.com>

On Tue, 25 Apr 2023 13:45:13 +0200
Pierre Morel <pmorel@linux.ibm.com> wrote:

> On 4/25/23 13:33, Janosch Frank wrote:
> > On 4/25/23 12:53, Pierre Morel wrote:  
> >>
> >> On 4/25/23 10:26, Claudio Imbrenda wrote:  
> >>> On Mon, 24 Apr 2023 19:42:18 +0200
> >>> Pierre Morel <pmorel@linux.ibm.com> wrote:
> >>>  
> >
> > How is this considered to be a fix and not a workaround?
> >
> >
> > Set the variable response bit in the control mask and vary the length 
> > based on stfle 140. See __init sclp_early_read_info() in 
> > drivers/s390/char/sclp_early_core.c  

I agree that the SCLP needs to be fixed

> 
> 
> Yes it is something to do anyway.
> 
> Still in case of error we will need this fix or workaround.

and I agree that we need this fix anyway

therefore the comment should be more generic and just mention the fact
that the test would hang if an abort happens before SCLP Read SCP
Information has completed.

> 
> 
> >
> >  
> >>>  
> >>>> Fixes: 52076a63d569 ("s390x: Consolidate sclp read info")
> >>>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> >>>> ---
> >>>>    lib/s390x/sclp.c | 5 +++--
> >>>>    1 file changed, 3 insertions(+), 2 deletions(-)
> >>>>
> >>>> diff --git a/lib/s390x/sclp.c b/lib/s390x/sclp.c
> >>>> index acdc8a9..c09360d 100644
> >>>> --- a/lib/s390x/sclp.c
> >>>> +++ b/lib/s390x/sclp.c
> >>>> @@ -119,8 +119,9 @@ void sclp_read_info(void)
> >>>>       int sclp_get_cpu_num(void)
> >>>>    {
> >>>> -    assert(read_info);
> >>>> -    return read_info->entries_cpu;
> >>>> +    if (read_info)
> >>>> +        return read_info->entries_cpu;
> >>>> +    return 1;
> >>>>    }
> >>>>       CPUEntry *sclp_get_cpu_entries(void)  
> >  


  reply	other threads:[~2023-04-25 12:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 17:42 [kvm-unit-tests PATCH 0/1] Fixing infinite loop on SCLP READ SCP INFO error Pierre Morel
2023-04-24 17:42 ` [kvm-unit-tests PATCH 1/1] s390x: sclp: consider monoprocessor on read_info error Pierre Morel
2023-04-25  8:26   ` Claudio Imbrenda
2023-04-25 10:53     ` Pierre Morel
2023-04-25 11:33       ` Janosch Frank
2023-04-25 11:45         ` Pierre Morel
2023-04-25 12:16           ` Claudio Imbrenda [this message]
2023-04-25 13:24             ` Pierre Morel
2023-04-25 13:48         ` Pierre Morel

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=20230425141634.1e18b172@p-imbrenda \
    --to=imbrenda@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=nsg@linux.ibm.com \
    --cc=pmorel@linux.ibm.com \
    --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