[Top] [All Lists]

Re: Kernel link address assumption

To: Himanshu Chauhan <>
Subject: Re: Kernel link address assumption
From: "Kevin D. Kissell" <>
Date: Thu, 24 Feb 2011 13:44:01 -0800
Cc: linux-mips <>
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default;; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Source:X-Source-Args:X-Source-Dir; b=WdYHIlaCy7V2ChT+yFoR8Jq8CwNbRScPmVFMoi/ZLfTzrxL5ydCw7eGy+ppWzCrJatPg1oX7NIvqPXPLuQJC4zkHsUH3n2haWuiLhfaK3DxrUVqYipWRf9aMbr4rq1h3;
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101208 Thunderbird/3.1.7
On 02/24/11 10:21, Himanshu Chauhan wrote:
On Thursday 24 February 2011 11:46 PM, Kevin D. Kissell wrote:
On 02/24/11 10:13, Himanshu Chauhan wrote:

Does Linux kernel for MIPS assumes that its link address is always in Kseg0?
What if I change the link address to somewhere in useg?
Your page fault handlers will be in for an interesting time. ;o)

What you describe can be, and is done, for virtualized kernels running on top of a hypervisor, but there's a bit more involved than just changing the link address.

You just caught that. Thats what I am trying to evaluate. What all I would need to do apart from changing the link address. I am working on a bare metal hypervisor for MIPS architecture.

Any pointers?

I've done a design of something like this for a non-MIPS architecture, but I'd prefer someone who's done this for MIPS (and I know that there are people out there who have) advise you.


            Kevin K.

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