X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8216E.5306DBFA@onstor-exch02.onstor.net>; Wed, 7 Nov 2007 10:45:10 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: chassisd accessing kernel memory
Date: Wed, 7 Nov 2007 10:45:10 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E06793E55@onstor-exch02.onstor.net>
In-Reply-To: <20071107103859.3f5e9a41@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: chassisd accessing kernel memory
Thread-Index: AcghbXbN1IIp/xsKQnOVO4Tb07HIqAAAEFBg
References: <20071107103859.3f5e9a41@ripper.onstor.net>
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	<dl-cougar>

Which offsets, which base address? What exactly is it you are
suggesting?=20

>-----Original Message-----
>From: Andy Sharp
>Sent: Wednesday, November 07, 2007 10:39 AM
>To: dl-cougar
>Subject: Fw: chassisd accessing kernel memory
>
>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
