All of lore.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, seiden@linux.ibm.com,
	scgl@linux.ibm.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v1 1/2] lib: s390x: terminate if PGM interrupt in interrupt handler
Date: Wed, 19 Oct 2022 11:51:28 +0200	[thread overview]
Message-ID: <20221019115128.2a8cbf13@p-imbrenda> (raw)
In-Reply-To: <166616486603.37435.2225106614844458657@t14-nrb>

On Wed, 19 Oct 2022 09:34:26 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:

> Quoting Claudio Imbrenda (2022-10-18 16:09:50)
> [...]
> > diff --git a/lib/s390x/interrupt.c b/lib/s390x/interrupt.c
> > index 7cc2c5fb..22bf443b 100644
> > --- a/lib/s390x/interrupt.c
> > +++ b/lib/s390x/interrupt.c  
> [...]
> >  void handle_pgm_int(struct stack_frame_int *stack)
> >  {
> > +       if (THIS_CPU->in_interrupt_handler) {
> > +               /* Something went very wrong, stop everything now without printing anything */
> > +               smp_teardown();
> > +               disabled_wait(0xfa12edbad21);
> > +       }  
> 
> Maybe I am missing something, but is there a particular reson why you don't do
>  THIS_CPU->in_interrupt_handler = true;
> here as well?

I was thinking that we set pgm_int_expected = false so we would catch a
wild program interrupt there, but in hindsight maybe it's better to set
in_interrupt_handler = true there so we can abort immediately

  reply	other threads:[~2022-10-19 11:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 14:09 [kvm-unit-tests PATCH v1 0/2] s390x misc fixes Claudio Imbrenda
2022-10-18 14:09 ` [kvm-unit-tests PATCH v1 1/2] lib: s390x: terminate if PGM interrupt in interrupt handler Claudio Imbrenda
2022-10-19  7:34   ` Nico Boehr
2022-10-19  9:51     ` Claudio Imbrenda [this message]
2022-10-20  7:58       ` Nico Boehr
2022-10-20  8:57         ` Claudio Imbrenda
2022-10-20 11:19           ` Janosch Frank
2022-10-20 11:45             ` Claudio Imbrenda
2022-10-20 12:12               ` Janosch Frank
2022-10-18 14:09 ` [kvm-unit-tests PATCH v1 2/2] s390x: uv-host: fix allocation of UV memory Claudio Imbrenda
2022-10-19  6:34   ` Janosch Frank
2022-10-20  8:07   ` Steffen Eiden

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=20221019115128.2a8cbf13@p-imbrenda \
    --to=imbrenda@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=scgl@linux.ibm.com \
    --cc=seiden@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 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.