[Top] [All Lists]

Re: how to use TLB to prevent Linux accessing a particular memory region

To: veerasena reddy <>
Subject: Re: how to use TLB to prevent Linux accessing a particular memory region
From: "J. Scott Kasten" <>
Date: Tue, 16 Oct 2007 10:13:38 -0400 (EDT)
Cc: "" <>, linux-mips <>
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;; h=Received:X-YMail-OSG:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To:Message-ID:References:MIME-Version:Content-Type; b=akM0+42tI/BIy9qBq8LPS2ng6yVM0NcC0Mg7LDGOlqtRIli5Wr9YpZeuBdIaixNDttJFESksHCINMFwCHFqiG2vS7FzlvI2rfr/auhTUYyrKQDRv5oz7LkK87KhaNiBKfoxR3mo3U/py+gO7SykHAKYdR4XhlJB06Qnu52+Og9M= ;
In-reply-to: <>
Original-recipient: rfc822;
References: <>

Really, it sounds more like you want a custom driver that "owns" that region of memory so it's marked as used and this driver is the gate keeper. I wonder if the console frame buffer driver for the mips ip32 arch might be a good example for you as it swallows a several meg chunk of memory for the display.


On Tue, 16 Oct 2007, veerasena reddy wrote:


I have a board, which has two processors ( one is MIPS
on which Linux-2.6.18 kernel runs and another is DSP
based processor) and 32MB DDR.

Out of 32MB of DDR 8MB is reserved for use by DSP
processor. But the MIPS processor downloads firmware
into this reserved memory for the DSP.

Now, is it possible to use the TLB to prevent Linux
from accessing the reserved memory after the firmware
has been downloaded?

Also we'd need to remove those TLB entries if the
firmware would ever need to be reloaded to the DSP'
memory region.

What are the APIs to be used to achieve the above?

Thanks in advance.


     5, 50, 500, 5000 - Store N number of mails in your inbox. Go to

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