From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by oss.sgi.com id ; Mon, 8 Jan 2001 08:37:48 -0800 Received: from brutus.conectiva.com.br ([200.250.58.146]:55797 "EHLO dhcp046.distro.conectiva") by oss.sgi.com with ESMTP id ; Mon, 8 Jan 2001 08:37:35 -0800 Received: (ralf@lappi.waldorf-gmbh.de) by bacchus.dhis.org id ; Mon, 8 Jan 2001 14:27:29 -0200 Date: Mon, 8 Jan 2001 14:27:29 -0200 From: Ralf Baechle To: "Maciej W. Rozycki" Cc: "Kevin D. Kissell" , linux-mips@oss.sgi.com, Carsten Langgaard , Michael Shmulevich Subject: Re: User applications Message-ID: <20010108142729.D886@bacchus.dhis.org> References: <010701c07986$ac768180$0deca8c0@Ulysses> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from macro@ds2.pg.gda.pl on Mon, Jan 08, 2001 at 04:40:06PM +0100 X-Accept-Language: de,en,fr Sender: owner-linux-mips@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-mips-outgoing On Mon, Jan 08, 2001 at 04:40:06PM +0100, Maciej W. Rozycki wrote: > > than flushing the caches - so long as by "flush" we mean invalidate > > with writeback (on copyback caches), of course. > > What's wrong with cacheflush(addr, count, which) that actually checks if > lies within the caller's address space before > performing the flush and returns -EPERM otherwise? It would make the > caller crawl like a turtle if it wished to but it would leave other > processes alone. cacheflush(2) actually is supposed to handle things that way. Ralf