From owner-freebsd-arch@FreeBSD.ORG  Sat Jan  4 04:14:51 2014
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 967C134E;
 Sat,  4 Jan 2014 04:14:51 +0000 (UTC)
Received: from mail-qe0-x230.google.com (mail-qe0-x230.google.com
 [IPv6:2607:f8b0:400d:c02::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 43BB71E4C;
 Sat,  4 Jan 2014 04:14:51 +0000 (UTC)
Received: by mail-qe0-f48.google.com with SMTP id gc15so16496067qeb.35
 for <multiple recipients>; Fri, 03 Jan 2014 20:14:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=D1x1eL5b2OBYSlcC08Of/x/8DxwChtXLW4Wc4hWWPjE=;
 b=b8r2YQnATzXYG999QGBWHZwPQR6PTAMXIIXnWXmgjfb3jHLP7+Y37BPT59kuVSAo02
 GIY3qVUT7u7M6n8tiJ5vZE7LVDKD2Ug82a409X7Ovyr/Eg7Q7uiDDJcon28wR40V1u6q
 cfeuP4UoS6+xzk3psAYHk6im7P22TMrxcIC3hbZ2uXM9eFkswU+fQvMD5Nh113HpnHgr
 a6/QeSTmTUHeJKXL8Q+bhQtXnvizzhKU4Y8yuxH95YP6y5nCFlPLg6hMjMtYTsZQzIDI
 funr1PQD++LyyITv/Ee5dt3RmycaD+D013Kv40ov9anAU0NtnYFYTI7NwixKmn2RTcRg
 sACw==
MIME-Version: 1.0
X-Received: by 10.224.14.132 with SMTP id g4mr48887831qaa.26.1388808890481;
 Fri, 03 Jan 2014 20:14:50 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.224.52.8 with HTTP; Fri, 3 Jan 2014 20:14:50 -0800 (PST)
In-Reply-To: <52C783DE.1060102@gmail.com>
References: <CAJ-Vmok-AJkz0THu72ThTdRhO2h1CnHwffq=cFZGZkbC=cWJZA@mail.gmail.com>
 <52C77DB8.5020305@gmail.com>
 <CAJ-Vmok=VSLiwzh-626qUWUuqJC1rtg58mwB_zqT2oQd64oo_Q@mail.gmail.com>
 <52C783DE.1060102@gmail.com>
Date: Fri, 3 Jan 2014 20:14:50 -0800
X-Google-Sender-Auth: xCkpTTl3UnId6p-rY5it5OsvDMg
Message-ID: <CAJ-Vmo=eWhhEc7fTzycjhphW8GPJK13u3APsCKbEVYbze_X=LQ@mail.gmail.com>
Subject: Re: Acquiring a lock on the same CPU that holds it - what can be done?
From: Adrian Chadd <adrian@freebsd.org>
To: David Xu <davidxu@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2014 04:14:51 -0000

On 3 January 2014 19:45, David Xu <listlog2011@gmail.com> wrote:

> Does critical_enter disable interrupts ? Long time ago, I saw it does
> not. If I remembered it correctly, spinlock_enter disables interrupt,
> critical_enter still allows interrupt, but current thread can not be
> preempted, it is deferred.

Ah there we go. Yes, okay. My bad.



-a