From: Piet/Pete Delaney <piet@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] anyone maintaining lkcd for ia64?
Date: Fri, 08 Feb 2002 00:35:52 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698806022@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698806015@msgid-missing>
On Thu, Feb 07, 2002 at 02:00:52PM -0600, Jack Steiner wrote:
> Hi piet
>
> Does the lkcd that you are working on support both SGI SN systems
> and DIG systems.
Most likely.
>
> The main difference is the patch that is required on SGI systems to
> support discontiguous memory.
What patch?
> Also, we use XSCSI for disk access. Is that an issue??
Looks like XSCSI isn't configured in n my 2.4.16 workspace:
#
# Alternate SCSI support
#
# CONFIG_XSCSI is not set
however it appears to have been turned on in the 2.4.16-product gate.
Sounds like it's a lot faster; does the root partition have to change
to support XSCSI on the lab machines like monica?
I think I'll delay upgrading my Workspace till after I check in the
current lkcd code. If it doesn't handle XSCSI I'll fix it.
BTW, how are things going on fixing kdb and linux so that breakpoints
work in 2.4.17? I haven't heard anything on how that's going or the fix
for the Machine Checks to non-existing memory that is mapped with the mmu.
> Are you working on a pure IA64 patch
I believe it's currently pure, I don't think I'm using anything from the sn1
directory. It's still in development, so we can change things based on
what come up.
To get more work done in parallel it likely better to get working code in
ASAP to avoid duplication of work.
-piet
> >
> > On Thu, Feb 07, 2002 at 10:51:26AM -0600, Robert K Gjertsen wrote:
> >
> > Hi Rob:
> >
> > I'm about 90% done on getting a preliminary version of lkcd working
> > for ia64. I hope to update the workspace shortly. I have to clean up
> > some of the changes I made to support the dump page size being smaller
> > that the virtual memory default page size.
> >
> > I hope to work out a put today with the EFI memory reading by lcrash,
> > how about I send you a copy tomarrow with some of the code cleaned up and
> > I'll check it in after I've made sure I haven't brooken ia32.
> >
> > -piet
> >
> > > I've used kdb in the past for ia64, but was
> > > taking a look at getting lkcd working on RH 7.2
> > > (2.4.9-18/21) for ia64.
> > > I grabbed the latest stuff from sourceforge.net
> > > and I'm working through the patched build now
> > > and see that dump_base.c is ia64 unfriendly
> > > with its use of irq_stat (using a hacked patch
> > > originally from lkcd-2.4.15-1.diff).
> > > I'm slogging through this, but I hate to reinvent
> > > the wheel if someone else has a working
> > > copy/patch (newer kernel version is fine).
> > > Anyone actually using this for newer kernels
> > > on ia64 (and has SGI totally dumped working
> > > on this)?
> > >
> > > Thanks,
> > >
> > > --Rob
> > >
> > >
> > > _______________________________________________
> > > Linux-IA64 mailing list
> > > Linux-IA64@linuxia64.org
> > > http://lists.linuxia64.org/lists/listinfo/linux-ia64
> >
> > _______________________________________________
> > Linux-IA64 mailing list
> > Linux-IA64@linuxia64.org
> > http://lists.linuxia64.org/lists/listinfo/linux-ia64
> >
>
>
> --
> Thanks
>
> Jack Steiner (651-683-5302) (vnet 233-5302) steiner@sgi.com
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2002-02-08 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 16:51 [Linux-ia64] anyone maintaining lkcd for ia64? Robert K Gjertsen
2002-02-07 18:14 ` Tom Morano
2002-02-07 19:29 ` Piet/Pete Delaney
2002-02-07 20:00 ` Jack Steiner
2002-02-08 0:35 ` Piet/Pete Delaney [this message]
2002-02-08 0:56 ` Jack Steiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698806022@msgid-missing \
--to=piet@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox