Date: Fri, 3 Jan 2014 20:14:50 -0800 From: Adrian Chadd <adrian@freebsd.org> To: David Xu <davidxu@freebsd.org> Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: Acquiring a lock on the same CPU that holds it - what can be done? Message-ID: <CAJ-Vmo=eWhhEc7fTzycjhphW8GPJK13u3APsCKbEVYbze_X=LQ@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=eWhhEc7fTzycjhphW8GPJK13u3APsCKbEVYbze_X=LQ>