Re: [PATCH 0/9] x86-64 put current in r10
From: Andi Kleen (ak_at_suse.de)
Date: 11/30/05
- Previous message: Johannes Stezenbach: "Re: [linux-dvb-maintainer] [PATCH] Fix budget-ci linking problem"
- In reply to: Jari Ruusu: "Re: [PATCH 0/9] x86-64 put current in r10"
- Next in thread: Andi Kleen: "Re: [PATCH 0/9] x86-64 put current in r10"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 30 Nov 2005 13:45:09 +0100 To: Jari Ruusu <jariruusu@users.sourceforge.net>
> Your patch breaks all out-of-tree amd64 assembler code used in kernel. r10
> register is one of those registers that does not need to be preserved across
> function calls, and reserving that register for other purpose means that all
> assembler code using r10 in kernel must be rewritten. This is deeply
> unfunny.
Well, the changes should be minor.
>
> Please don't apply Ben's patch. It is already bad enough having to deal with
> two incompatible calling conventions on 32 bit x86.
43KB .text savings are hard to argue against. There is no guarantee
for a stable kernel ABI. If you maintain out of tree code you
will need to live with the occasional changes.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Johannes Stezenbach: "Re: [linux-dvb-maintainer] [PATCH] Fix budget-ci linking problem"
- In reply to: Jari Ruusu: "Re: [PATCH 0/9] x86-64 put current in r10"
- Next in thread: Andi Kleen: "Re: [PATCH 0/9] x86-64 put current in r10"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
