linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allen Martin <amartin@nvidia.com>
To: <zanussi@kernel.org>
Cc: <linux-rt-users@vger.kernel.org>, <anup.pemmaiah@gmail.com>,
	<bigeasy@linutronix.de>
Subject: ARMv8 fp register corruption in 4.14 PREEMPT_RT series
Date: Wed, 27 Mar 2019 14:35:55 -0700	[thread overview]
Message-ID: <20190327213555.GA16845@nvidia.com> (raw)

Hi Tom, I can confirm the ARMv8 fp register corruption reported here:

https://marc.info/?l=linux-rt-users&m=153930857708206&w=2

still exists in 4.14.106-rt56.  I was able to reproduce this on both
A57 and Carmel ARMv8 CPUs using the float_bessel subtest of LTP.  This
fix was to backport the following patch from 4.18.y-rt to 4.14-rt:

  3afdfe419c33c1655d0763e070350aad44416594
  arm64: fpsimd: use preemp_disable in addition to local_bh_disable()

Are you able to pick up this patch into 4.14-rt?  I'm sure Anup and I
are not the only ones who are hitting this.

-Allen

             reply	other threads:[~2019-03-27 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 21:35 Allen Martin [this message]
2019-03-28 14:18 ` ARMv8 fp register corruption in 4.14 PREEMPT_RT series Tom Zanussi

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=20190327213555.GA16845@nvidia.com \
    --to=amartin@nvidia.com \
    --cc=anup.pemmaiah@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=zanussi@kernel.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 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).