From owner-freebsd-arch@FreeBSD.ORG  Sat Nov 15 16:41:39 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.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A23B98B1;
 Sat, 15 Nov 2014 16:41:39 +0000 (UTC)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com
 [IPv6:2a00:1450:400c:c00::229])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 31D42BAB;
 Sat, 15 Nov 2014 16:41:39 +0000 (UTC)
Received: by mail-wg0-f41.google.com with SMTP id y19so2405992wgg.28
 for <multiple recipients>; Sat, 15 Nov 2014 08:41:37 -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=cpyv0RVQK1oWDg+A4n7fqrJMlFn1oABJASb8vqARERQ=;
 b=Rr199YCD6gLzzuXOTRl4DqP/q186cgnRNdx0RUoxraeGKExDpC6tILtvbPiYMCejn5
 a9euPMlzrh3pGXCH6epopIEs0HGUs7jQuJz8Y91mBAZY484nhErsKXpa1hMSBM0IAzBG
 8avJxqC8eESsvV73WmB+e6wLcK4dZA/YQnL2FAKsNlHzGEhV/albf/vnb4lLpNgmWLOg
 gg45JfTGXLarRGwlgSgtRho8fGDH9HUlS1K3a0F/mhZuzMXRCZatidsS2PCVFicJNap7
 dyzwT/DhUTGFM28FAwOcoWnXeeAxSZCwZ0nul8Wii+Pu9QnNa1xTY3hvv/TyOYJtbsP7
 SUMg==
MIME-Version: 1.0
X-Received: by 10.194.47.226 with SMTP id g2mr23931263wjn.68.1416069697662;
 Sat, 15 Nov 2014 08:41:37 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.216.106.136 with HTTP; Sat, 15 Nov 2014 08:41:37 -0800 (PST)
In-Reply-To: <54676BA6.7000202@FreeBSD.org>
References: <201203202037.q2KKbNfK037014@svn.freebsd.org>
 <201203211502.14353.jkim@FreeBSD.org> <4F6AF1CB.80902@FreeBSD.org>
 <201203220748.49635.jhb@freebsd.org>
 <20120322141436.GC2358@deviant.kiev.zoral.com.ua>
 <54666FD5.6080705@FreeBSD.org> <20141115105819.GJ17068@kib.kiev.ua>
 <54676BA6.7000202@FreeBSD.org>
Date: Sat, 15 Nov 2014 08:41:37 -0800
X-Google-Sender-Auth: S5TIxPA5gvXL2pFbs6s3eS9Ugm4
Message-ID: <CAJ-Vmo=JbMRH0J4jy03sKxeMV-FP7GoE5R--92241rzeMTMo-g@mail.gmail.com>
Subject: Re: suspending threads before devices
From: Adrian Chadd <adrian@freebsd.org>
To: Andriy Gapon <avg@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: Konstantin Belousov <kostikbel@gmail.com>, Jung-uk Kim <jkim@freebsd.org>,
 "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.18-1
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, 15 Nov 2014 16:41:39 -0000

[snip]

Hm, would just creating a suspend kernel thread make it easier?

Ie, instead of you doing the suspend in the context of the calling
process, just have it signal to a kernel thread, so the userland
thread doing the suspend can also be suspended?



-adrian