X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C82300.4DAEF19C@onstor-exch02.onstor.net>; Fri, 9 Nov 2007 10:42:39 -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: Fri, 9 Nov 2007 10:42:39 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E06794C3A@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E06794BF8@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: chassisd accessing kernel memory
Thread-Index: AcghetXpDk/s1LaVSWKDbM1qIH+9cwBgu5GQAAByY8A=
References: <BB375AF679D4A34E9CA8DFA650E2B04E066D200A@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E06793EE6@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E06793EEC@onstor-exch02.onstor.net> <20071107121442.4fdf4249@ripper.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E06794BF8@onstor-exch02.onstor.net>
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

Ok, it was wrong question. Everybody please reply if you are working on
that driver or not.

>-----Original Message-----
>From: Maxim Kozlovsky
>Sent: Friday, November 09, 2007 10:25 AM
>To: Andy Sharp
>Cc: Tim Gardner; dl-Cougar
>Subject: RE: chassisd accessing kernel memory
>
>So is anybody working on that driver for the chassisd?
>
>>-----Original Message-----
>>From: Andy Sharp
>>Sent: Wednesday, November 07, 2007 12:15 PM
>>To: Maxim Kozlovsky
>>Cc: Tim Gardner; dl-Cougar
>>Subject: Re: chassisd accessing kernel memory
>>
>>On Wed, 7 Nov 2007 11:34:58 -0800 "Maxim Kozlovsky"
>><maxim.kozlovsky@onstor.com> wrote:
>>
>>>
>>>
>>> _____________________________________________
>>> From: Tim Gardner
>>> Sent: Wednesday, November 07, 2007 11:33 AM
>>> To: Maxim Kozlovsky; dl-Cougar
>>> Subject: RE: chassisd accessing kernel memory
>>>
>>> Do all the addresses that chassisd access reside in a 32bit window?
>>> [MK] No.
>>
>>Huh?  Sure they do.  In fact, < 32bit window, methinks.  What address
>>does chassisd access that isn't between [physical] 0x10000000 -
>>0x1fffffff ?
>>
>>>  If so, we could simply extend mem.c to provide another /dev/port
like
>>> driver that
>>> adds an offset to every address.
>>> [MK] How is that different from what I've just said?
>>
>>Doing what I said is far easier.
>>
>>____________________________________________
>>> From: Maxim Kozlovsky
>>> Sent: Wednesday, November 07, 2007 8:44 AM
>>> To: dl-Cougar
>>> Subject: chassisd accessing kernel memory
>>>
>>> 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.
>>>
