AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071107103850.6d286495@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<dl-cougar>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
FMID:#mh/Mailbox/sent	0	20071107103814.1c2b1352@ripper.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 7 Nov 2007 10:38:59 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: dl-cougar
Subject: Fw: chassisd accessing kernel memory
Message-ID: <20071107103859.3f5e9a41@ripper.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

Oopsie, meant to send this to the list.

Begin forwarded message:

Date: Wed, 7 Nov 2007 10:38:14 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
Subject: Re: chassisd accessing kernel memory


On Wed, 7 Nov 2007 08:43:32 -0800 "Maxim Kozlovsky"
<maxim.kozlovsky@onstor.com> wrote:

> It turns out with the 64 bit kernel accessing the kernel memory from
> /dev/port no longer works, since it requires reading at negative 64
> bit offsets like 0xffffffffb0000000. Looks like we'll have to stop
> cheating and write a separate driver.

Cheating?  Well, if we were cheating before we can certainly keep on
cheating now.  We just have to get a little clever.  Like having a
base address that is platform specific and always use offsets in the
code.

Cheers,

a
