AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071011172129.04e5eab1@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<rick.lund@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E05FEA34C@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 11 Oct 2007 17:22:10 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Cc: "Rick Lund" <rick.lund@onstor.com>
Subject: Re: swarm CFE access
Message-ID: <20071011172210.271b6e44@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E05FEA34C@onstor-exch02.onstor.net>
References: <20071011111053.2c3d913c@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E05FEA261@onstor-exch02.onstor.net>
	<20071011145029.162def52@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E05FEA34C@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

It's my understanding, which maybe I should bone up on some more, is
that CKSSEG is a predefined map just like CKSEG0-2, only it is a funky
32-bit compatibility magicland.

So, code that runs there can have pointers that are 32 bit and they are
treated as if they were 64 bit pointers that amount to

(((pointer value in code) - 0x8000.0000) | 0xffff.ffff.c000.0000)

[ok, algo not entirely correct: pointers in code are supposedly linked
to run in a 32-bit KSEG0 is what I mean]

That's my kindegarden level understanding and I'm not sure that's even
correct.

Probably not much help, sorry.

But I can boot a 64-bit kernel on the swarm and load modules w/o it
crashing and burning.  If you're running in 32 bit mode, 0xc000.0000
means something else entirely, and I don't think that is even useable
until after you toggle the BEV bit.  Or whatever that bit is called
that is set when the prom code is running.

Cheers,

a

On Thu, 11 Oct 2007 16:17:30 -0700 "Brian Stark"
<brian.stark@onstor.com> wrote:

> Andy,
> 
> We're still pretty confused on what the cksseg region is supposed to
> do. Since it's a mapped space, we've set up TLB entries to point to a
> physical address starting at 0xc000.0000.  When we access the virtual
> address, the processor crashes with a DBE, meaning that nothing was
> at a physical address of 0xc000.0000 (which there isn't).
> 
> So, a couple of questions:
> 
> - What physical space is cksseg supposed to map to?
> - Can you tell from the kernel what virtual address is being used to
> access cksseg?
> 
> 
> Brian
>  
> 
> > -----Original Message-----
> > From: Andy Sharp 
> > Sent: Thursday, October 11, 2007 2:50 PM
> > To: Rick Lund
> > Cc: Brian Stark
> > Subject: Re: swarm CFE access
> > 
> > Hi Rick,
> > 
> > I forgot to mention that I also added brians to the acl for 
> > this session so you can use his login as well as your own, 
> > assuming as I did that they even gave you one.
> > 
> > Let me know if you still have problems.
> > 
> > Cheers,
> > 
> > a
> > 
> > On Thu, 11 Oct 2007 14:34:19 -0700 "Rick Lund"
> > <rick.lund@onstor.com> wrote:
> > 
> > > brians@ripper:/$ screen -r andys/ub.console Access to 
> > session denied.
> > > 
> > > -----Original Message-----
> > > From: Andy Sharp
> > > Sent: Thursday, October 11, 2007 11:11 AM
> > > To: Brian Stark
> > > Cc: Rick Lund
> > > Subject: swarm CFE access
> > > 
> > > Well, this hopefully works.  If it does, it will be very simple.
> > > 
> > > Log into ripper:
> > > 
> > > $ slogin ripper
> > > 
> > > then, issue this command:
> > > 
> > > ripper$ screen -r andys/ub.console
> > > 
> > > if you get an error from that command, let me know, otherwise,
> > > you should now be talking to the CFE.  you should see the prompt.
> > > 
> > > inadequate DNS settings on your computer may require you to say 
> > > something like 'ripper.onstor.net' or such...
> > > 
> > > Let me know how it goes.
> > > 
> > > I'm getting a lot of interest from the community about this 
> > CF paging 
> > > issue.  Of course, it's a different issue, but I thought I 
> > would let 
> > > you know they are thinking about us.
> > > 
> > > Cheers,
> > > 
> > > a
> > 
