From: Keith Owens <kaos@sgi.com>
To: ilya@theIlya.com
Cc: linux-mips@linux-mips.org
Subject: Re: Yet another fix
Date: Mon, 02 Jun 2003 23:27:46 +1000 [thread overview]
Message-ID: <5368.1054560466@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 01 Jun 2003 21:57:00 MST." <20030602045700.GI3035@gateway.total-knowledge.com>
On Sun, 1 Jun 2003 21:57:00 -0700,
ilya@theIlya.com wrote:
>module_map is referenced in register_ioctl32_conversion in arch/mips64/ioctl32.c
>As far as I can see, it should simply be possible to replace module_map
>with vmalloc in there, but I am not sure, as I don't know how exactly
>ioctl translations work...
Not in 2.4.20 nor 2.4.21-rc6 from Marcelo, must be a mips local change.
I strongly suggest that you get rid of it, there is no good reason to
emulate the 32 bit module syscalls on a 64 bit machine. modutils is
pure Linux and there is absolutely no justification for emulating 32
bit versions of modutils when the user can install the 64 bit version
of modutils instead. 32 bit emulation is a crutch to let binary only
programs work when you do not have the source to rebuild to 64 bit, by
definition we have the source to modutils.
IA64 and x86_64 make no attempt to emulate 32 bit modutils. sparc64,
ppc64 and s390x all pass the data straight to the 64 bit kernel code,
they require the user space modutils to supply 64 bit data. Emulation
is a waste of time.
next prev parent reply other threads:[~2003-06-02 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 4:14 Yet another fix ilya
2003-06-02 4:49 ` Keith Owens
2003-06-02 4:57 ` ilya
2003-06-02 13:27 ` Keith Owens [this message]
2003-06-02 14:12 ` Ralf Baechle
2003-06-02 14:30 ` ilya
2003-06-02 23:50 ` Keith Owens
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=5368.1054560466@ocs3.intra.ocs.com.au \
--to=kaos@sgi.com \
--cc=ilya@theIlya.com \
--cc=linux-mips@linux-mips.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