From owner-freebsd-alpha Wed Jul 10 6:59:49 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD79F37B400; Wed, 10 Jul 2002 06:59:46 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EA6943E09; Wed, 10 Jul 2002 06:59:46 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 JAA10425; Wed, 10 Jul 2002 09:59:43 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6ADxDT39518; Wed, 10 Jul 2002 09:59:13 -0400 (EDT) (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: <15660.15793.332512.618094@grasshopper.cs.duke.edu> Date: Wed, 10 Jul 2002 09:59:13 -0400 (EDT) To: Peter Wemm Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: uac flags in the kernel In-Reply-To: <20020709224221.E98DB3808@overcee.wemm.org> References: <20020709224221.E98DB3808@overcee.wemm.org> 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 Peter Wemm writes: > John Baldwin wrote: > > Ok, I have a couple of questions about the uac (unaligned access check) > > flags in the kernel. First, I think they should be a process-wide > > property, so we need to move them out of td_md.md_flags and into a > > p_md.md_flags or p_md.md_uac or some such. Secondly, why do the > > sysarch() syscalls get and set the uac of the parent process? > > uac works on the parent, because it would be a bit silly to work on > itself since it is just about to exit. > > Actually, I'd like it to behave more like env(1)/ktrace etc. > > uac ... - operates on parent > uac -p nnn ... - operates on process nnn > uac ... /bin/sh - execs /bin/sh with specified uac settings. All this sounds fine, except for the -p flag, which currently disables printing of unaligned access errors. FWIW, the uac flags were named so as to be compatable with the Tru64 uac routine for users migrating from Tru64. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message