From owner-freebsd-hackers Mon Mar 6 16:13: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by hub.freebsd.org (Postfix) with ESMTP id 7C62737BDEC for ; Mon, 6 Mar 2000 16:12:58 -0800 (PST) (envelope-from chris@holly.calldei.com) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id SAA09142; Mon, 6 Mar 2000 18:14:05 -0600 (CST) (envelope-from chris) Date: Mon, 6 Mar 2000 18:14:05 -0600 From: Chris Costello To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Where is pci_intr_establish() & _thread_sys_read()? Message-ID: <20000306181404.H4990@holly.calldei.com> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: X-URL: http://www.FreeBSD.org/~chris/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, March 06, 2000, Zhihui Zhang wrote: > Can anyone tell me where is the code for pci_intr_establish() and > _thread_sys_read()? I could not find them under /usr/src. I can tell you offhand that _thread_sys_anything is the _real_ syscall for `anything'. This is because a lot of syscalls are reimplemented within libc_r for reasons that are kind of obvious (directly calling the read syscall from one thread would block all the other threads in a process). So _thread_sys_open() == open(2), _thread_sys_read() == read(2), etc. I don't know about pci_intr_establish. -- |Chris Costello |Today's assembler command : EXOP Execute Operator `---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message