From owner-freebsd-bugs@freebsd.org  Mon Sep 18 19:13:54 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEF7FE000D0
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon, 18 Sep 2017 19:13:54 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CCF8C777F5
 for <freebsd-bugs@FreeBSD.org>; Mon, 18 Sep 2017 19:13:54 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v8IJDsmw023364
 for <freebsd-bugs@FreeBSD.org>; Mon, 18 Sep 2017 19:13:54 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 222234] head -r323246 aarch64 (Pine64+ 2GB) boot time context,
 sometimes: acquiring blockable sleep lock with spinlock or critical section
 held
Date: Mon, 18 Sep 2017 19:13:54 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: markmi@dsl-only.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-222234-8-4Re1khX2oW@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-222234-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-222234-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Sep 2017 19:13:55 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222234

--- Comment #6 from Mark Millard <markmi@dsl-only.net> ---
Created attachment 186517
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D186517&action=
=3Dedit
Example patch for sys/arm64/arm64/identcpu.c 's sev instruction use

Beyond the release_aps use of SEV during boot
I found a SEV use in identcpus.c . So this is
a possible patch for that (for the same issue
of SEV not being timed relative to memory
updates).

I do not claim either patch has the optimal
form of dsb ??? instruction, just one that
seems (more then?) sufficient.

--=20
You are receiving this mail because:
You are the assignee for the bug.=