From owner-freebsd-bugs@freebsd.org  Wed Oct 21 18:54:38 2015
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 11C68A1AF77
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 21 Oct 2015 18:54:38 +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 F26C1993
 for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 2015 18:54:37 +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 t9LIsbA4074762
 for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 2015 18:54:37 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 203941] arm64 IMPLEMENT ME: dtrace_toxic_ranges
Date: Wed, 21 Oct 2015 18:54:38 +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: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: emaste@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-203941-8-8EjBhFLp7m@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203941-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-203941-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.20
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: Wed, 21 Oct 2015 18:54:38 -0000

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

--- Comment #1 from Ed Maste <emaste@freebsd.org> ---
And for quick reference:

/*
 * DTrace Toxic Ranges
 *
 * DTrace supports safe loads from probe context; if the address turns out to  
 * be invalid, a bit will be set by the kernel indicating that DTrace
 * encountered a memory error, and DTrace will propagate the error to the user 
 * accordingly.  However, there may exist some regions of memory in which an   
 * arbitrary load can change system state, and from which it is impossible to  
 * recover from such a load after it has been attempted.  Examples of this may 
 * include memory in which programmable I/O registers are mapped (for which a  
 * read may have some implications for the device) or (in the specific case of 
 * UltraSPARC-I and -II) the virtual address hole.  The platform is required   
 * to make DTrace aware of these toxic ranges; DTrace will then check that     
 * target addresses are not in a toxic range before attempting to issue a      
 * safe load.
 */

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