From owner-freebsd-current@freebsd.org Wed Jul 1 19:16:09 2015 Return-Path: Delivered-To: freebsd-current@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 31BCC99182B for ; Wed, 1 Jul 2015 19:16:09 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 1F88023F6; Wed, 1 Jul 2015 19:16:09 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id EA3CF5AC; Wed, 1 Jul 2015 19:16:07 +0000 (UTC) Date: Wed, 1 Jul 2015 19:16:06 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-current@freebsd.org Message-ID: <39422495.82.1435778167308.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1880188576.78.1435747165254.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1880188576.78.1435747165254.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD-tests - Build #1153 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD-tests X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2015 19:16:09 -0000 FreeBSD_HEAD-tests - Build #1153 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1153/ to view the results. From owner-freebsd-current@freebsd.org Wed Jul 1 19:45:00 2015 Return-Path: Delivered-To: freebsd-current@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 80201991D8D for ; Wed, 1 Jul 2015 19:45:00 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D8E9100B for ; Wed, 1 Jul 2015 19:45:00 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by igblr2 with SMTP id lr2so105298573igb.0 for ; Wed, 01 Jul 2015 12:44:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+nvl8c/A0NvkoIveEVZhud++dFf6YesOp9I4Gzfokmg=; b=hgh1tAGrB/9fQaRLK1Yuxxp+WE16ED6ol9giWgcxIEp4UvTUnmIt6k0KZgSfuwN6pf dPVkDKafe6Box7/DofZZVxQdsT/o0PiDMadafi/MeazzIMkpuaiSq1ss8AXcUqqg7/ww GeM0xHAQZZARHayfUBo8qcMyvzASmQVE5/TY+IL0dRNNNll1HI+Q41aOqf4s2GiZYp2P L2r3QhLxxrlSoLSLJZx7bQ2HjaR/Ukfloc5jomToNN7+eKL47YPskxjgcVOkv4fRrp6M L1lJvEuYgjeZd70jFKII61IIb8YxVlTRuApmLB2OMblcTJoOm02trz7lz5M67IfN3/2s DLdQ== MIME-Version: 1.0 X-Received: by 10.107.33.146 with SMTP id h140mr41502428ioh.1.1435779899614; Wed, 01 Jul 2015 12:44:59 -0700 (PDT) Received: by 10.107.145.68 with HTTP; Wed, 1 Jul 2015 12:44:59 -0700 (PDT) Date: Wed, 1 Jul 2015 15:44:59 -0400 Message-ID: Subject: How should a driver shutdown a taskqueue on detach? From: Ryan Stone To: FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2015 19:45:00 -0000 I'm trying to figure out how a driver is supposed to shut down its interrupt-handling taskqueue when it detaches. taskqueue(9) recommends disabling interrupts, draining each task and then freeing the taskqueue. The problem that I have is the interrupt-handling tasks will sometimes re-enable interrupts on the device. Is there a better way than using some kind of flag internally in the driver to note that a detach is in progress that the interrupt handlers will have to check before enabling interrupts?