AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071109104443.393b0dc3@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<maxim.kozlovsky@onstor.com>,<tim.gardner@onstor.com>,<dl-Cougar@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	BB375AF679D4A34E9CA8DFA650E2B04E06794C3A@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 9 Nov 2007 10:44:59 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>, "dl-Cougar"
 <dl-Cougar@onstor.com>
Subject: Re: chassisd accessing kernel memory
Message-ID: <20071109104459.24ff4f11@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E06794C3A@onstor-exch02.onstor.net>
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>
	<BB375AF679D4A34E9CA8DFA650E2B04E06794C3A@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

This currently on Rendell's plate, although I think he's not working on
it this exact moment.  Rendell?

On Fri, 9 Nov 2007 10:42:39 -0800 "Maxim Kozlovsky"
<maxim.kozlovsky@onstor.com> wrote:

> 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.
> >>>
