From: Andi Kleen <ak@suse.de>
To: devnetfs <devnetfs@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel modules and 64-bit kernels
Date: 27 Jan 2003 19:52:38 +0100 [thread overview]
Message-ID: <p73n0lmzaq1.fsf@oldwotan.suse.de> (raw)
In-Reply-To: devnetfs's message of "27 Jan 2003 19:05:18 +0100"
devnetfs <devnetfs@yahoo.com> writes:
> Do kernel modules need to be aware that they are running in a 64-bit
> kernel or a 32-bit kernel?
Yes, if they want to support 32bit programs in a 64bit kernel they
usually need ioctl translation and sometimes syscall translation
(if they have own ioctls or syscalls)
> How should be the modules be written so they work both on 32/64-bit
> kernel AND can interact with both 32/64-bit userspace programs in
> a 64-bit kernel??
http://www.firstfloor.org/~andi/writing-ioctl32
-Andi
next parent reply other threads:[~2003-01-27 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030127180414.85643.qmail@web20417.mail.yahoo.com.suse.lists.linux.kernel>
2003-01-27 18:52 ` Andi Kleen [this message]
2003-01-27 18:04 devnetfs
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=p73n0lmzaq1.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=devnetfs@yahoo.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®