All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Boehr <nrb@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com
Subject: [kvm-unit-tests PATCH v2 0/3] s390x: add tests for SIGP call orders in enabled wait
Date: Fri, 22 Jul 2022 09:20:01 +0200	[thread overview]
Message-ID: <20220722072004.800792-1-nrb@linux.ibm.com> (raw)

v1->v2:
---
* rebase to latest master to align with Claudio's SMP changes, drop
  patch which adds the ext int clean up since it is already in Claudio's
  series
* make sure ctl0 register bit is cleared

When a CPU is in enabled wait, it can still receive SIGP calls from
other CPUs.

Since this requires some special handling in KVM, we should have tests
for it. This has already revealed a KVM bug with ecall under PV, which
is why this test currently fails there.

Some refactoring is done as part of this series to reduce code
duplication.

Nico Boehr (3):
  s390x: smp: move sigp calls with invalid cpu address to array
  s390x: smp: use an array for sigp calls
  s390x: smp: add tests for calls in wait state

 s390x/smp.c | 190 +++++++++++++++++++++++++++++-----------------------
 1 file changed, 108 insertions(+), 82 deletions(-)

-- 
2.36.1


             reply	other threads:[~2022-07-22  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  7:20 Nico Boehr [this message]
2022-07-22  7:20 ` [kvm-unit-tests PATCH v2 1/3] s390x: smp: move sigp calls with invalid cpu address to array Nico Boehr
2022-07-22  8:00   ` Janosch Frank
2022-07-22  7:20 ` [kvm-unit-tests PATCH v2 2/3] s390x: smp: use an array for sigp calls Nico Boehr
2022-07-22  8:13   ` Janosch Frank
2022-07-22  7:20 ` [kvm-unit-tests PATCH v2 3/3] s390x: smp: add tests for calls in wait state Nico Boehr
2022-07-22  8:30   ` Janosch Frank
2022-07-22 11:08     ` 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=20220722072004.800792-1-nrb@linux.ibm.com \
    --to=nrb@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.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.