Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: parisc-linux@lists.parisc-linux.org,
	Kyle McMartin <kyle@parisc-linux.org>
Subject: Re: [parisc-linux] alternate insn for parisc (ccio/sba)
Date: Sat, 04 Mar 2006 11:21:41 +0800	[thread overview]
Message-ID: <440907C5.7050503@tausq.org> (raw)
In-Reply-To: <20060304003802.GB18473@colo.lackof.org>

> Anyplace we use asm that could be different for PA20 vs PA11.
> __ffs() in include/asm/bitops.h probaby isn't the best example
> but it might be good enough to give an idea.
> Ie kernel built for PA11 could be optimized for PA20-32bit.

Just my 2 cents, but unless it is code that is performance critical and
we can demonstrate a significant difference on a particular measurement,
and it is not something that can be determined at compile time, I think
we should do runtime code patching sparingly. If nothing else, it makes
the code harder to read and perhaps to debug.

>> Also, if you want to test it, you'll need to remove the & ~_PAGE_WRITE from
>> PAGE_KERNEL_RO in asm/pgtable.h until we write protect the kernel at a
>> later stage.

Right - it seems we should re-map the kernel read-only after you patch
the insns.

> very cool! ++kyle. :)

it is cool, thanks for working on this, Kyle.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2006-03-04  3:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03 20:14 [parisc-linux] alternate insn for parisc (ccio/sba) Kyle McMartin
2006-03-04  0:38 ` Grant Grundler
2006-03-04  0:35   ` Kyle McMartin
2006-03-04  3:21   ` Randolph Chung [this message]
2006-03-06 17:07     ` Grant Grundler
2006-03-06 16:05   ` Kyle McMartin
2006-03-06 17:20     ` 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=440907C5.7050503@tausq.org \
    --to=randolph@tausq.org \
    --cc=grundler@parisc-linux.org \
    --cc=kyle@parisc-linux.org \
    --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