linux-mips
[Top] [All Lists]

Re: cacheops.h & r4kcache.h

To: Mohamed Bamakhrama <bamakhrama@gmail.com>
Subject: Re: cacheops.h & r4kcache.h
From: Ralf Baechle <ralf@linux-mips.org>
Date: Wed, 1 Aug 2007 15:40:01 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <40378e40708010713p3d866a9dva7d69132e61497d6@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <40378e40708010618r7a93e58br206e7c47e685a05e@mail.gmail.com> <20070801140114.GA23858@linux-mips.org> <40378e40708010713p3d866a9dva7d69132e61497d6@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.14 (2007-02-12)
On Wed, Aug 01, 2007 at 04:13:05PM +0200, Mohamed Bamakhrama wrote:

> I agree with you that it fits more to real-time systems. My point was
> that such a functionality can be added to the list of available macros
> (i.e. Fetch, invalidate) so that when the developer (of an embedded
> system for example) needs it, he/she can use it directly.
> 
> Is it possible to submit a patch which adds this functionality?

It takes more than a small patch to add a few cacheop definitions.  Linux
generiously uses Index cacheops and so would also blow away wired cache
lines and that would need to be prevented.  But to answer your question,
with these notes, yes.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>