mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Roland Dreier <rdreier@cisco.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Trying to convert old modules to newer kernels
Date: Fri, 21 Dec 2007 09:39:59 -0500	[thread overview]
Message-ID: <20071221143959.GG2308@csclub.uwaterloo.ca> (raw)
In-Reply-To: <Pine.LNX.4.61.0712201755330.9907@chaos.analogic.com>

On Thu, Dec 20, 2007 at 05:56:19PM -0500, linux-os (Dick Johnson) wrote:
> Okay. Thanks! I need to do that.

On the (now somewhat old) 2.6.18 kernel I use it is an option under
"Processor type and features" called "Use register arguments", but yeah
it isn't an option anymore in new kernels.

As for your argument that it isn't a good idea, well most of the time
the arguments you want to pass to a function are already values you were
just working with to get them ready for the function, so quite likely
they are already in the registers you are worried about having to clear
first.  Add to that the ability of modern x86 CPUs to use rename
registers to fake stack accesses in some cases and the clearing of the
registers become pretty much a non issue, at least that's my
understanding of how things work.

--
Len Sorensen

  reply	other threads:[~2007-12-21 14:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 20:10 linux-os (Dick Johnson)
2007-12-19 20:23 ` Lennart Sorensen
2007-12-19 20:56   ` linux-os (Dick Johnson)
2007-12-20 15:02     ` Lennart Sorensen
2007-12-20 16:13       ` linux-os (Dick Johnson)
2007-12-20 16:27         ` Lennart Sorensen
2007-12-20 21:23           ` linux-os (Dick Johnson)
2007-12-20 21:40             ` Roland Dreier
2007-12-20 22:56               ` linux-os (Dick Johnson)
2007-12-21 14:39                 ` Lennart Sorensen [this message]
2007-12-21 16:37                   ` linux-os (Dick Johnson)
2007-12-29 14:19           ` Jon Masters
2007-12-20 18:28         ` Sam Ravnborg
2007-12-20 21:27           ` linux-os (Dick Johnson)
2007-12-20 22:05             ` Sam Ravnborg
2007-12-20 23:05               ` linux-os (Dick Johnson)
2007-12-20 23:53                 ` J.A. Magallón
2007-12-21 12:08                   ` James Courtier-Dutton
2007-12-21 12:43                     ` Jan Engelhardt
2007-12-27  0:17                     ` Bill Davidsen
2007-12-21 14:43             ` Lennart Sorensen
2007-12-21 16:39               ` linux-os (Dick Johnson)
2007-12-27  0:19               ` Bill Davidsen
2007-12-19 20:47 ` Jan Engelhardt
2007-12-19 21:10   ` linux-os (Dick Johnson)
2007-12-19 21:16     ` Jan Engelhardt
2007-12-19 20:52 ` Sam Ravnborg
     [not found] <9CdyE-1A6-7@gated-at.bofh.it>
     [not found] ` <9CdIw-1Op-29@gated-at.bofh.it>
     [not found]   ` <9Cebz-2sz-29@gated-at.bofh.it>
     [not found]     ` <9Cvcw-5mu-15@gated-at.bofh.it>
     [not found]       ` <9CwhY-76J-11@gated-at.bofh.it>
     [not found]         ` <9Cyk3-1Zc-29@gated-at.bofh.it>
     [not found]           ` <9CB8a-6zV-13@gated-at.bofh.it>
2007-12-21  0:16             ` Bodo Eggert
2007-12-21 13:11               ` linux-os (Dick Johnson)

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=20071221143959.GG2308@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=rdreier@cisco.com \
    /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

all inboxes | Powered by JetHome®