From owner-freebsd-current@FreeBSD.ORG Mon Jan 14 14:32:39 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2949616A417; Mon, 14 Jan 2008 14:32:39 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 0C2A113C4F2; Mon, 14 Jan 2008 14:32:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 6A2CD1A4D86; Mon, 14 Jan 2008 06:29:26 -0800 (PST) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 14 Jan 2008 09:20:11 -0500 User-Agent: KMail/1.9.7 References: <478A739F.2030003@FreeBSD.org> <20080114110054.GK17508@fasolt.home.paeps.cx> In-Reply-To: <20080114110054.GK17508@fasolt.home.paeps.cx> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801140920.12890.jhb@freebsd.org> Cc: jls@freebsd.org, current@freebsd.org Subject: Re: mpsafe psm driver needed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 14 Jan 2008 14:32:39 -0000 On Monday 14 January 2008 06:00:54 am Philip Paeps wrote: > On 2008-01-13 21:25:03 (+0100), Kris Kennaway wrote: > > I've been looking at some mutex profiling traces from users of 6.x and 7.x > > who are reporting that their mouse pointer sometimes freezes when their > > system is busy. In most of the situations I have looked at this is because > > the psm driver is Giant-locked, and competes with other things like the > > syncer (in 6.x), or sysctl calls (I have a WIP for this that I need to > > revisit). > > > > This is a minor problem from a grand architectural point of view but an > > important one from a usability point of view. I believe these particular > > interactivity problems would be resolved if the psm driver no longer > > required Giant. Is anyone able to work on this? > > I have taken a look at this in the past. It's not a trivial problem. > > There is a lot of what I can only charitably call "legacy code" in psm and it > appears that as soon as you touch any of it, it upsets at least one brand of > KVM "out there". > > One of my mentees has been working on a rewrite for a while, but the project > has not yet been committed to cvs. > > jls: any news on this? Does psm(4) interface with any subsystems like tty(4)? -- John Baldwin