From: Matthew Wilcox <[EMAIL PROTECTED]> Subject: Re: RFC: is_compat_task (Was: Re: input compat stuff) Date: Tue, 28 Jun 2005 12:18:28 +0100
> On Tue, Jun 28, 2005 at 11:17:04AM +0200, Andi Kleen wrote: > > No, it's not because it makes it impossible to have 64bit processes > > that run with 32bit ABI (not implemented right now but we don't > > want to break that). > > > > Please don't do this. It is absolutely the wrong thing to do. > > So. You want to deliver a signal to a task. How do you know whether > to send it a 64-bit signal or a 32-bit signal? There is a difference between syscal ABI and execution ABI. I think Andi is kind of right about this. Why don't we do the following to resolve this issue? Create a "is_compat_syscall()" macro, in compat syscall trap entry, the bit is set, and it is cleared otherwise. It nops out to always evaluate to "0" on non-compat platforms. That should resolve all of the concerns, I think.
