Date: Fri, 23 Mar 2001 21:16:37 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: arch@FreeBSD.org, Bruce Evans <bde@zeta.org.au> Subject: Re: Critical Regions Round II Message-ID: <XFMail.010323211637.jhb@FreeBSD.org> In-Reply-To: <XFMail.010323182607.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24-Mar-01 John Baldwin wrote: >> This was really a renaming of the x86-specific interfaces read_eflags() >> and write_eflags(). I object to the x86 code being changed to use the >> new names. The x86 code that disables interrupts mostly wants precisely >> the MD interfaces, not the MI abstraction of them. It just happens that >> the MI versions are binary-identical with the MD versions. > > Ok, I could go with that. (/me deletes half of his patch.) Actually, I thought about this some more. Most of the places that do this (for example, before setting cr0 or something else critical) don't really care about any of the flags values, they are just keeping from being preempted, so I think that using critical_* in those places is more appropriate. If something needs to read eflags and act on it, then one would use read_eflags(). MD code still calls MI functions in other places. -- John Baldwin <jhb@FreeBSD.org> -- 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 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?XFMail.010323211637.jhb>