public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Nico Boehr <nrb@linux.ibm.com>,
	Pierre Morel <pmorel@linux.ibm.com>,
	linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, kvm@vger.kernel.org,
	imbrenda@linux.ibm.com, david@redhat.com, nsg@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v10 2/2] s390x: topology: Checking Configuration Topology Information
Date: Tue, 11 Jul 2023 10:43:25 +0200	[thread overview]
Message-ID: <6c690eb9-06b1-a5e8-4875-e0d83f8d1ce7@redhat.com> (raw)
In-Reply-To: <168906286416.9488.17612605115280167157@t14-nrb>

On 11/07/2023 10.07, Nico Boehr wrote:
> Quoting Thomas Huth (2023-07-10 16:38:22)
>> On 10/07/2023 10.36, Nico Boehr wrote:
>>> Quoting Thomas Huth (2023-07-06 12:48:50)
>>> [...]
>>>> Does this patch series depend on some other patches that are not upstream
>>>> yet? I just tried to run the test, but I'm only getting:
>>>>
>>>>     lib/s390x/sclp.c:122: assert failed: read_info
>>>>
>>>> Any ideas what could be wrong?
>>>
>>> Yep, as you guessed this depends on:
>>> Fixing infinite loop on SCLP READ SCP INFO error
>>> https://lore.kernel.org/all/20230601164537.31769-1-pmorel@linux.ibm.com/
>>
>> Ok, that fixes the assertion, but now I get a test failure:
>>
>> ABORT: READ_SCP_INFO failed
>>
>> What else could I be missing?
> 
> Argh, I forgot that you need this fixup to the patch:
> https://lore.kernel.org/all/269afffb-2d56-3b2f-9d83-485d0d29fab5@linux.ibm.com/
> 
> If that doesn't work, let me know, so I can try and reproduce it here.

Thank you very much, removing that line fixed the problem, indeed. Both 
topology tests are passing now on my z15 LPAR.

Tested-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2023-07-11  8:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  8:21 [kvm-unit-tests PATCH v10 0/2] S390x: CPU Topology Information Pierre Morel
2023-06-27  8:21 ` [kvm-unit-tests PATCH v10 1/2] s390x: topology: Check the Perform Topology Function Pierre Morel
2023-06-29  8:49   ` Nico Boehr
2023-06-29 12:53     ` Pierre Morel
2023-07-03  8:42     ` Thomas Huth
2023-07-12  9:09       ` Pierre Morel
2023-07-12  9:10       ` Pierre Morel
2023-06-27  8:21 ` [kvm-unit-tests PATCH v10 2/2] s390x: topology: Checking Configuration Topology Information Pierre Morel
2023-06-29  8:47   ` Nico Boehr
2023-07-06 10:48   ` Thomas Huth
2023-07-10  8:36     ` Nico Boehr
2023-07-10 14:38       ` Thomas Huth
2023-07-11  8:07         ` Nico Boehr
2023-07-11  8:43           ` Thomas Huth [this message]
2023-07-12  9:08             ` Pierre Morel
2023-06-30 12:29 ` [kvm-unit-tests PATCH v10 0/2] S390x: CPU " Nico Boehr

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=6c690eb9-06b1-a5e8-4875-e0d83f8d1ce7@redhat.com \
    --to=thuth@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@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 \
    /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