From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, scgl@linux.ibm.com,
nrb@linux.ibm.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 3/3] lib: s390x: better smp interrupt checks
Date: Mon, 27 Jun 2022 11:28:18 +0200 [thread overview]
Message-ID: <19169d83-ad31-da70-b3bb-bd7ba43e6484@linux.ibm.com> (raw)
In-Reply-To: <20220624144518.66573-4-imbrenda@linux.ibm.com>
On 6/24/22 16:45, Claudio Imbrenda wrote:
> Use per-CPU flags and callbacks for Program and Extern interrupts,
> instead of global variables.
>
> This allows for more accurate error handling; a CPU waiting for an
> interrupt will not have it "stolen" by a different CPU that was not
> supposed to wait for one, and now two CPUs can wait for interrupts at
> the same time.
>
> This will significantly improve error reporting and debugging when
> things go wrong.
>
> Both program interrupts and extern interrupts are now CPU-bound, even
> though some extern interrupts are floating (notably, the SCLP
> interrupt). In those cases, the testcases should mask interrupts and/or
> expect them appropriately according to need.
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> lib/s390x/asm/arch_def.h | 17 +++++++++++-
> lib/s390x/smp.h | 8 +-----
> lib/s390x/interrupt.c | 57 +++++++++++++++++++++++++++++-----------
> lib/s390x/smp.c | 11 ++++++++
> 4 files changed, 70 insertions(+), 23 deletions(-)
[...]
>
> +struct lowcore *smp_get_lowcore(uint16_t idx)
> +{
> + if (THIS_CPU->idx == idx)
> + return &lowcore;
> +
> + check_idx(idx);
> + return cpus[idx].lowcore;
> +}
This function is unused.
> +
> int smp_sigp(uint16_t idx, uint8_t order, unsigned long parm, uint32_t *status)
> {
> check_idx(idx);
> @@ -253,6 +262,7 @@ static int smp_cpu_setup_nolock(uint16_t idx, struct psw psw)
>
> /* Copy all exception psws. */
> memcpy(lc, cpus[0].lowcore, 512);
> + lc->this_cpu = cpus + idx;
Why not:
lc->this_cpu = &cpus[idx];
>
> /* Setup stack */
> cpus[idx].stack = (uint64_t *)alloc_pages(2);
> @@ -325,6 +335,7 @@ void smp_setup(void)
> for (i = 0; i < num; i++) {
> cpus[i].addr = entry[i].address;
> cpus[i].active = false;
> + cpus[i].idx = i;
> /*
> * Fill in the boot CPU. If the boot CPU is not at index 0,
> * swap it with the one at index 0. This guarantees that the
next prev parent reply other threads:[~2022-06-27 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:45 [kvm-unit-tests PATCH v2 0/3] better smp interrupt checks Claudio Imbrenda
2022-06-24 14:45 ` [kvm-unit-tests PATCH v2 1/3] lib: s390x: add functions to set and clear PSW bits Claudio Imbrenda
2022-06-27 8:35 ` Janosch Frank
2022-06-27 10:47 ` Claudio Imbrenda
2022-06-24 14:45 ` [kvm-unit-tests PATCH v2 2/3] s390x: skey.c: rework the interrupt handler Claudio Imbrenda
2022-06-24 14:45 ` [kvm-unit-tests PATCH v2 3/3] lib: s390x: better smp interrupt checks Claudio Imbrenda
2022-06-27 9:28 ` Janosch Frank [this message]
2022-06-27 10:53 ` Claudio Imbrenda
2022-06-27 11:09 ` Janosch Frank
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=19169d83-ad31-da70-b3bb-bd7ba43e6484@linux.ibm.com \
--to=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=scgl@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