All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: peter.maydell@linaro.org, qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/intc/arm_gicv3_cpuif: Tolerate spurious EOIR writes
Date: Thu, 3 Jun 2021 15:14:05 +0200	[thread overview]
Message-ID: <YLjVnWV7ZgEj/cpw@myrica> (raw)
In-Reply-To: <31c4e422-5451-3c0a-f5e6-df75559c9a9b@redhat.com>

On Thu, Jun 03, 2021 at 02:39:30PM +0200, Philippe Mathieu-Daudé wrote:
> > diff --git a/hw/intc/arm_gicv3_cpuif.c b/hw/intc/arm_gicv3_cpuif.c
> > index 81f94c7f4a..1d0964c9bf 100644
> > --- a/hw/intc/arm_gicv3_cpuif.c
> > +++ b/hw/intc/arm_gicv3_cpuif.c
> > @@ -1357,7 +1357,8 @@ static void icc_eoir_write(CPUARMState *env, const ARMCPRegInfo *ri,
> >          }
> >          break;
> >      default:
> > -        g_assert_not_reached();
> > +        /* No interrupt was active, this is UNPREDICTABLE. Ignore it. */
> 
> A qemu_log_mask(LOG_GUEST_ERROR, ...) call here could be useful,
> do you mind adding it?

No problem. I had it at first, but then wondered if that meant I should
update similar cases in the GIC device that silently ignore guest errors
at the moment (e.g. the guest writes a number > 1023 to EOIR) and decided
against it. I'll resend with only this error report if there is no
objection.

Thanks,
Jean

> > +        return;
> >      }
> >  
> >      icc_drop_prio(cs, grp);
> > 
> 


  reply	other threads:[~2021-06-03 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 11:00 [PATCH] hw/intc/arm_gicv3_cpuif: Tolerate spurious EOIR writes Jean-Philippe Brucker
2021-06-03 12:39 ` Philippe Mathieu-Daudé
2021-06-03 13:14   ` Jean-Philippe Brucker [this message]
2021-06-03 12:56 ` Peter Maydell
2021-06-03 14:52   ` Shashi Mallela

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=YLjVnWV7ZgEj/cpw@myrica \
    --to=jean-philippe@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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.