All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] alternate insn for parisc (ccio/sba)
Date: Mon, 6 Mar 2006 10:20:42 -0700	[thread overview]
Message-ID: <20060306172042.GD21702@colo.lackof.org> (raw)
In-Reply-To: <20060306160515.GB3208@quicksilver.road.mcmartin.ca>

On Mon, Mar 06, 2006 at 11:05:15AM -0500, Kyle McMartin wrote:
> I just got an idea for fixing the indirect calls style thing... Would it
> be possible to do "run time" relocation of certain indirect calls if we
> know they won't ever differ for a given kernel boot?

dma_ops table doesn't change once it's initialized.
But I've still got Randolph's caution rattling around in my head.

>  I guess it wouldn't
> be too terribly difficult if the linker would just leave certain relocations
> unprocessed, and make sure all possible, for example, dma_ops function
> pointers were reachable from the given stub? 

dma_ops map/unmap calls are in performance critical code path.
It would be helpful to get rid of the indirect dma_ops calls IFF the
resulting code is supportable. ie the average driver writer needs
to be able to follow it.

thanks,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

      reply	other threads:[~2006-03-06 17:20 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
2006-03-06 17:07     ` Grant Grundler
2006-03-06 16:05   ` Kyle McMartin
2006-03-06 17:20     ` Grant Grundler [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=20060306172042.GD21702@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=kyle@mcmartin.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.