From owner-freebsd-alpha Tue Dec 18 11:35:24 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id DF0FD37B41A; Tue, 18 Dec 2001 11:35:19 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA15109; Tue, 18 Dec 2001 14:35:14 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id fBIJYnh16840; Tue, 18 Dec 2001 14:34:49 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15391.39513.362355.537968@grasshopper.cs.duke.edu> Date: Tue, 18 Dec 2001 14:34:49 -0500 (EST) To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: mdproc flags in KSE In-Reply-To: References: <15391.37056.22312.225550@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin writes: <...> > > > sure about the other ones. What is the HAE and in what contexts is it > > used? > > > > Its used by programs, like the X server, which grovel around in PCI > > memory space... Hmm.. In a quick browse through the code, I don't see > > where its actually used anymore.. > > My question is more this: would it be a process property or a thread property? > So, if a process turns on HAE access, does a few things, and later on turns it > off, it becomes a process property (or even worse, a userland thread property > which becomes a pain to handle in KSE). Whereas, if this is something done > entirely in a kernel context and the flag is just used to handle things > properly while switching and faulting while in kernel context, it can be a > thread property. We need to ask Doug about this.. <...> > > Its used only by OSFF/ECOFF binaries. It is setup each time osf1_sigaction() > > is called & used at sigreturn time to point to that process's > > sigtramp code. Tru64 does'nt just keep it in a standard place like we > > do. > > So it gets regenerated on the fly and should probably be per-thread? Well, > except that do we want multiple threads sending signals down to the userland > scheduler? Ugh. I'll leave it per-thread for now. OSF1/ECOFF is a foreign ABI, somewhat like linux/elf. I doubt that OSF1/ECOFF programs will ever know about or use more than one thread per process (or KSE, or whatever the KSE name for a schedulable entity is). Does that help at all?? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message