linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [rfc 4.16-rt patch] arm64: efi,fpsimd: use a local_lock() in efi_virtmap_load()
Date: Thu, 26 Jul 2018 19:52:01 +0200	[thread overview]
Message-ID: <1532627521.6124.13.camel@gmx.de> (raw)
In-Reply-To: <20180726150934.tsrk6kgc2nmhbxq2@linutronix.de>

On Thu, 2018-07-26 at 17:09 +0200, Sebastian Andrzej Siewior wrote:
> On 2018-07-11 17:07:22 [+0200], Mike Galbraith wrote:
> > Greetings,
> > 
> > With the patch below, there's still one neon splat to figure out what
> > to do with should this patch not die a gruesome death.  Cavium box
> > boots and seemingly works fine modulo kvm, which is utterly deadly in
> > 4.16-rt due to..
> > 
> > 972             if (!vgic_initialized(vcpu->kvm))
> > 973                     return false;
> > 974
> > 975             irq = vgic_get_irq(vcpu->kvm, vcpu, vintid);
> > 976             spin_lock_irqsave(&irq->irq_lock, flags);
> > 
> > ..that lock apparently having wandered into a minefield post v4.14.
> > 
> > Remaining neon splat:
> 
> I don't have this with preempt-disable patch for kernel_neon_begin()
> (posted seconds ago).

Oh, forget you _ever saw_ that patch.  It later demonstrated it's
"correctness" quite convincingly.  I didn't explicitly recall it due to
the patch it tried to build upon proving in the end to be a bit south
of wonderful itself, making the whole exercise a "let's make a bad
situation even worse" kinda thing :)

	-Mike

      reply	other threads:[~2018-07-26 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 15:07 [rfc 4.16-rt patch] arm64: efi,fpsimd: use a local_lock() in efi_virtmap_load() Mike Galbraith
2018-07-12  1:08 ` Steven Rostedt
2018-07-26 15:09 ` Sebastian Andrzej Siewior
2018-07-26 17:52   ` Mike Galbraith [this message]

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=1532627521.6124.13.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).