Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: Matthew Wilcox <willy@debian.org>, parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: [parisc-linux-cvs] linux grundler
Date: Sun, 9 Feb 2003 12:29:13 +0000	[thread overview]
Message-ID: <20030209122913.G27544@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030209031014.GD19683@dsl2.external.hp.com>; from grundler@dsl2.external.hp.com on Sat, Feb 08, 2003 at 08:10:14PM -0700

On Sat, Feb 08, 2003 at 08:10:14PM -0700, Grant Grundler wrote:
> Just drop that in debian/patches before building the debs.
> That patch applies clean to the binutils for unstable.
> I don't even pretend to understand how to properly build
> debian packages, much less binutils or "cross release" builds.
> That's why I made the tarball for "testing".

OK.  It's not really hard, but I don't mind doing it.  It's not like
this is a regular occurrence.  It's building now; when I've finished
I'll upload it to unofficial-debs and people will be able to apt-get
install it from there.

> I don't care to find out the hard way.
> I'd rather just comply with the architecture and not worry about it.
> If someone can demonstrate a perf advantage or issue, I'll be
> more receptive.

Sure.  When someone's trying to implement futexes, this may prove critical..

> > One final point.... up till now, we've been telling people it's OK to
> > run kernels configured for PA1.1 on PA2.0 processors.  This patch says
> > to me that's not safe.
> 
> Only for SMP. I think for UP the rule still holds.

Agree.  That was implicit in the kernel list i gave later, but I should've
stated it explicitly.

> Unfortunately yes.
> 
> OTOH, PA20 SMP still hasn't proven stable so maybe it's not worth
> doing at the moment either.  Once PA20 SMP is stable, we could drop
> the 64-bit UP kernels since most systems that *require* 64-bit are SMP.

Sure, but there's a measurable performance difference if you compile out
spinlocks

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  reply	other threads:[~2003-02-09 12:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030208222242.AA3554829@dsl2.external.hp.com>
     [not found] ` <20030208222746.GB19683@dsl2.external.hp.com>
2003-02-08 23:23   ` [parisc-linux] Re: [parisc-linux-cvs] linux grundler Matthew Wilcox
2003-02-09  0:35     ` John David Anglin
2003-02-09  0:49       ` Randolph Chung
2003-02-09  0:56         ` Randolph Chung
2003-02-09  2:03           ` Matthew Wilcox
2003-02-09  2:18             ` John David Anglin
2003-02-09 14:55             ` James Bottomley
2003-02-09  2:11           ` John David Anglin
2003-02-09  3:27       ` Grant Grundler
2003-02-09  4:06         ` John David Anglin
2003-02-09  3:10     ` Grant Grundler
2003-02-09 12:29       ` Matthew Wilcox [this message]
2003-02-09 14:35         ` Matthew Wilcox
2003-02-09 19:14         ` Grant Grundler
2003-02-09 21:24           ` Aaron St. Pierre
2003-02-10 16:47             ` Grant Grundler
2003-02-09 23:56           ` Randolph Chung
2003-02-09  8:11     ` Grant Grundler
2003-02-09 12:21       ` Matthew Wilcox
2003-07-09 10:35 Joel Soete
     [not found] <20030708022259.B62B849404E@palinux.hppa>
2003-07-08 15:06 ` Carlos O'Donell
  -- strict thread matches above, loose matches on Subject: below --
2003-02-10  8:38 John Marvin
2003-02-09  8:55 [parisc-linux] " John Marvin
2003-02-09  7:40 John Marvin
2003-02-09  8:26 ` [parisc-linux] " Grant Grundler
     [not found] <20020804011707.2B9164860@dsl2.external.hp.com>
2002-08-04  2:03 ` Grant Grundler

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=20030209122913.G27544@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=grundler@dsl2.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.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