From owner-cvs-all Tue Feb 27 11:29:12 2001 Delivered-To: cvs-all@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 9AAAF37B719; Tue, 27 Feb 2001 11:29:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1RJP5l80797; Tue, 27 Feb 2001 11:25:20 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 27 Feb 2001 11:28:20 -0800 (PST) From: John Baldwin To: Seigo Tanimura Subject: RE: cvs commit: src/sys/dev/sound/isa emu8000.c gusmidi.c mpu.c Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, tanimura@FreeBSD.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Feb-01 Seigo Tanimura wrote: > On Mon, 26 Feb 2001 10:50:52 -0800 (PST), > John Baldwin said: > >>> - Mutexify midi(4). The driver runs under the giant lock by default. >>> If you ever want to run midi(4) out of the giant lock, uncomment >>> MIDI_OUTOFGIANT in midi.h. Confirmed to work for csamidi with WITNESS >>> and INVARIANTS. > > John> Err, I hope that you do all mutex operations regardless, and only use > this > > I will do that in my next commit. Ok. > John> option to control setting the INTR_MPSAFE flag for any interrupt > handlers that > John> midi uses. > > Since some interrupt handlers are shared with pcm(4), we have to wait > for pcm(4) to be MP-safe. That is ok. > A couple of questions to ask: > > A. As we might hold a mutex of VM and block, malloc(9) should be > called with holding no mutexes except for Giant. Is that right? Don't do anything with Giant right now. The only thing you should be doing at all in relation to Giant is possibly setting the INTR_MPSAFE flag to mark an interrupt handler as MP safe and thus not needing Giant. > B. Is PI_AV for a multimedia device? If so, I would like to add > INTR_TYPE_AV to enum intr_type and ithread_priority() so that pcm and > midi devices can interrupt at PI_AV. Jake is the one to ask about the new priorities. If PI_AV is for multimedia stuff, then these flags sound ok, but you probably want to run it by the new-bus@FreeBSD.org list first. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message