From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Brian Gerst <bgerst@quark.didntduck.org>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Regparm for x86 machine check handlers
Date: Mon, 15 Nov 2004 13:54:24 -0800 [thread overview]
Message-ID: <41992590.4060004@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0411151201580.2222@ppc970.osdl.org>
Linus Torvalds wrote:
>
> On Mon, 15 Nov 2004, Brian Gerst wrote:
>
>>The patch to change traps and interrupts to the fastcall convention
>>missed the machine check handlers.
>
>
> Thanks, that was silly.
>
> Anybody want to write a script that verifies that the only remaining
> "asmlinkage" entries are of the type "sys_xxxx()"?
Is part of the problem definition missing here?
or I missed it?
E.g., printk() and vprint() are asmlinkage but not sys_xyz()...
but I have a suspicion that they are OK.
> "grep" shows that there's a number of incorrect ones left, but most of
> them seem to take no arguments, so ir doesn't matter. And there's the FP
> emulation stuff, which really -does- use the old interfaces.
so ignore the FP emulation, ignore functions with no arguments, right?
and omit "asmlinkage.*sys_xyz". that leaves a handful of functions
which are <asm>, like:
acpi_status asmlinkage acpi_enter_sleep_state(u8 sleep_state);
csum_partial(), csum_partial_copy_generic(),
schedule_tail(), aes_enc_blk(), aes_dec_blk().
I don't see others than need to be fixed, but a script
would be a safer way to check, so I'm trying to nail down
the requirements ... and what tool to use, like is there
already a PERL [or python or xyz] script that parses C,
or would you *coff* recommend sparse?
--
~Randy
next prev parent reply other threads:[~2004-11-15 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 17:42 [PATCH] Regparm for x86 machine check handlers Brian Gerst
2004-11-15 20:05 ` Linus Torvalds
2004-11-15 21:54 ` Randy.Dunlap [this message]
2004-11-15 23:10 ` Linus Torvalds
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=41992590.4060004@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=bgerst@quark.didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.