[Top] [All Lists]

Re: TAKE 981498 - Use KM_NOFS for debug trace buffers

To: Bhagi rathi <jahnu77@xxxxxxxxx>
Subject: Re: TAKE 981498 - Use KM_NOFS for debug trace buffers
From: Donald Douwsma <donaldd@xxxxxxx>
Date: Mon, 11 Aug 2008 18:07:10 +1000
Cc: Lachlan McIlroy <lachlan@xxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <cc7060690808072216q29efacf4tdf363fe3ed8a2c44@xxxxxxxxxxxxxx>
References: <20080806061553.A8D8958C52A4@xxxxxxxxxxxxxxxxxxxxxxx> <cc7060690808061012x43511581m15c794e72129becc@xxxxxxxxxxxxxx> <20080806201957.GQ21635@disturbed> <cc7060690808071043r659aea9fn4e28959b3a62081e@xxxxxxxxxxxxxx> <cc7060690808072216q29efacf4tdf363fe3ed8a2c44@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird (X11/20080724)
Bhagi rathi wrote:
> On Thu, Aug 7, 2008 at 11:13 PM, Bhagi rathi <jahnu77@xxxxxxxxx> wrote:
>>  By the way, I browse the source code from lxr.linux.no.
>>  If I have to browse the latest xfs source code with linux
>>  kernel that is used at SGI, how can I do that?
>  Any pointers on this? I wish to setup my own xfs development enviroment
>  and details on this will be helpful.

We maintain a CVS tree of xfs-dev on oss. It's slightly different to mainline
linux as it contains patches to include kdb and dmapi.

From the web page:

Set the CVSROOT environment variable.
 $ export CVSROOT=':pserver:cvs@xxxxxxxxxxx:/cvs'
 (for sh, bash, ksh, or similar shells)
 $ setenv CVSROOT  :pserver:cvs@xxxxxxxxxxx:/cvs
 (for csh or tcsh shells)

Login to the CVS server (this only needs to be done ONCE, not every time you 
access CVS).
$ cvs login
 (the password is "cvs")

Now grab the XFS source tree(s) of interest:
 $ cvs checkout linux-2.6-xfs
 $ cvs checkout xfs-cmds

Subsequently, you can checkout new code using:
 $ cvs update -d

<Prev in Thread] Current Thread [Next in Thread>