From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
frankja@linux.ibm.com, scgl@linux.ibm.com, pmorel@linux.ibm.com,
thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v1 2/2] lib: s390x: better smp interrupt checks
Date: Tue, 7 Jun 2022 16:41:13 +0200 [thread overview]
Message-ID: <20220607164113.5d51f37d@p-imbrenda> (raw)
In-Reply-To: <20220607162309.25e97913@li-ca45c2cc-336f-11b2-a85c-c6e71de567f1>
On Tue, 7 Jun 2022 16:23:09 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:
> On Fri, 3 Jun 2022 17:40:37 +0200
> Claudio Imbrenda <imbrenda@linux.ibm.com> wrote:
>
> > 0x1200 */ diff --git a/lib/s390x/interrupt.c b/lib/s390x/interrupt.c
> > index 27d3b767..e57946f0 100644
> [...]
> > @@ -30,7 +27,7 @@ void expect_pgm_int(void)
> >
> > void expect_ext_int(void)
> > {
> > - ext_int_expected = true;
> > + lc->ext_int_expected = 1;
>
> External Interrupts can be floating; so if I am not mistaken it could be delivered to a different CPU which didn't expect it.
yes I have considered that (maybe I should add this in the patch
description)
for floating interrupts, the testcase should take care to mask the
interrupt on the CPUs where it should not be received.
by default all interrupts are masked anyway and CPUs should only enable
them on a case by case basis
>
> [...]
> > @@ -237,17 +231,17 @@ void handle_io_int(void)
> >
> > int register_io_int_func(void (*f)(void))
> > {
> > - if (io_int_func)
> > + if (lc->io_int_func)
> > return -1;
>
> IO interrupts also are floating. Same concern as for the external interrupts.
same here
the alternative is to have a separate handling of floating vs
non-floating interrupts, which maybe would get a little out of hand
next prev parent reply other threads:[~2022-06-07 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 15:40 [kvm-unit-tests PATCH v1 0/2] better smp interrupt checks Claudio Imbrenda
2022-06-03 15:40 ` [kvm-unit-tests PATCH v1 1/2] s390x: skey.c: rework the interrupt handler Claudio Imbrenda
2022-06-07 13:29 ` Nico Boehr
2022-06-03 15:40 ` [kvm-unit-tests PATCH v1 2/2] lib: s390x: better smp interrupt checks Claudio Imbrenda
2022-06-07 10:01 ` Janis Schoetterl-Glausch
2022-06-07 11:08 ` Claudio Imbrenda
2022-06-07 14:23 ` Nico Boehr
2022-06-07 14:41 ` Claudio Imbrenda [this message]
2022-06-07 14:48 ` Nico Boehr
2022-06-07 16:43 ` Claudio Imbrenda
2022-06-10 9:43 ` 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=20220607164113.5d51f37d@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=pmorel@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