Date: Sat, 27 May 2000 00:26:47 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Chuck Paterson <cp@bsdi.com> Cc: Matthew Dillon <dillon@apollo.backplane.com>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, Terry Lambert <tlambert@primenet.com>, arch@FreeBSD.ORG Subject: Re: Preemptive kernel on older X86 hardware Message-ID: <392E97B7.1A575FAC@newsguy.com> References: <200005251700.LAA25373@berserker.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Paterson wrote: > > Almost.) I certainly think that the actually locking > stuff can be in a function but we really want to wrap the > function in a macro so we can put tracing in. Being able > to look at a trace and see file and line numbers for mutex > locks and unlocks is invaluable. Won't declaring the function as inline work? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@another.bsdconspiracy.org "Sentience hurts." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?392E97B7.1A575FAC>