From: Shanti Katta <katta@csee.wvu.edu>
To: Ben Collins <bcollins@debian.org>
Cc: sparc-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: Reg Sparc memory addresses
Date: 26 Sep 2002 13:54:57 -0400 [thread overview]
Message-ID: <1033062898.2037.43.camel@indus> (raw)
In-Reply-To: <20020926015645.GE28289@phunnypharm.org>
On Wed, 2002-09-25 at 21:56, Ben Collins wrote:
> On Wed, Sep 25, 2002 at 10:01:15PM -0400, Shanti Katta wrote:
> > Hi,
> > I compiled user-mode-linux kernel on Ultrasparc with load address set to
> > 00000000e0000000. But, when I try to debug the kernel, it just says
> > cannot access memory at address 0xa00020b0.
> > This error message remains the same no matter what I change the load
> > address to. Can anyone guide me on valid memory addresses for userspace
> > on Sparc? and how much different is that from x86 architecture?
>
> You compiled it on ultrasparc, but I hope you compiled it as a "sparc"
> target and not "sparc64".
I compiled UML as "sparc64".
> I'm not familiar with how UML runs in user space, but I suspect it needs
> to think it is sparc and not sparc64 for it to run in 32bit sparc
> userspace (which is what ultrasparc runs at for most cases).
>
So, I guess I need to compile UML as "sparc" target and debug it. I am
not sure how much of UML code runs in kernelspace and how much in
userspace. So, do I need to compile only the userspace code for UML as
"sparc" target or the whole of UML?
-Shanti
next prev parent reply other threads:[~2002-09-26 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 2:01 Reg Sparc memory addresses Shanti Katta
2002-09-26 1:56 ` Ben Collins
2002-09-26 4:42 ` Jeff Dike
2002-09-26 17:54 ` Shanti Katta [this message]
2002-09-26 17:50 ` Ben Collins
2002-09-26 18:19 ` [uml-devel] " Jeff Dike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1033062898.2037.43.camel@indus \
--to=katta@csee.wvu.edu \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparc-linux@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.