From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: How to intercept system calls on ia64 linux kernel
Date: Mon, 31 Jan 2005 17:34:32 +0000 [thread overview]
Message-ID: <16894.27688.84989.561686@napali.hpl.hp.com> (raw)
In-Reply-To: <b3b26beb050130195674d2930c@mail.gmail.com>
Note that it is very dangerous to compile kernel modules like so:
>>>>> On Mon, 31 Jan 2005 11:56:43 +0800, JinShan Xiong <jinshan.xiong@gmail.com> said:
JinShan> gcc -c -D__KERNEL__ -DMODULE -I/lib/modules/`uname
This is missing the -mfixed-rangeñ2-f15,f32-f127 option, which means
that more complicated modules will end up trashing floating-point
registers which means that your module will cause random crashes in
user-level codes. I'd recommend to compile modules the same way as normal
kernel code, except that you need to remove the -mconstant-gp flag.
In 2.6, this has gotten a lot easier, since modules are built using
the normal kbuild infrastructure.
--david
next prev parent reply other threads:[~2005-01-31 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 3:56 How to intercept system calls on ia64 linux kernel JinShan Xiong
2005-01-31 17:34 ` David Mosberger [this message]
2005-02-01 2:53 ` JinShan Xiong
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=16894.27688.84989.561686@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.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