From: "Broadfoot, KenX" <kenx.broadfoot@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] kdb v1.7 for IA64 is available
Date: Tue, 06 Feb 2001 16:43:46 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005119@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005109@msgid-missing>
I like this version of kdb a lot.
However I am looking forward to the 2.4.1 version even more as 2.4.1-010131
fixes alot of unaligned memory access problems I was seeing.
--ken
> -----Original Message-----
> From: Keith Owens [SMTP:kaos@ocs.com.au]
> Sent: Monday, February 05, 2001 6:35 PM
> To: Michael Madore
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] kdb v1.7 for IA64 is available
>
> On Mon, 5 Feb 2001 16:33:27 -0800,
> Michael Madore <mmadore@turbolinux.com> wrote:
> >Keith Owens wrote
> >> http://oss.sgi.com/projects/kdb/download/ia64/ contains kdb v1.7 for
> >> IA64, using the same design as kdb for i386. This is completely
> >> incompatible with HP's version of kdb, use one or the other but not
> >> both.
> >>
> >
> >Is there an advantage to using one of these implementations over the
> other?
>
> SGI's version of kdb was redesigned some months ago to better handle
> SMP, as well as recursion and debugging of kdb itself. Unless David
> Mosberger or Stephane Eranian have any objections[*], SGI will take
> over kdb for IA64 again.
>
> [*] Yes David, I _will_ remove the switch_stack change.
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
prev parent reply other threads:[~2001-02-06 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 3:53 [Linux-ia64] kdb v1.7 for IA64 is available Keith Owens
2001-02-06 0:33 ` Michael Madore
2001-02-06 2:34 ` Keith Owens
2001-02-06 2:48 ` David Mosberger
2001-02-06 16:43 ` Broadfoot, KenX [this message]
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-105590693005119@msgid-missing \
--to=kenx.broadfoot@intel.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