lkml.org 
[lkml]   [2012]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Compat 32-bit syscall entry from 64-bit task!?
On 01/18/2012 01:51 PM, Roland McGrath wrote:
>
> There are all the concerns about obscure ABI compatibility with
> expectations of existing debuggers and so forth, which Linus has mentioned.
> For that I can accept his point that things today so mishandle the
> int80-from-64 case that something like a new meaning for high bits of
> orig_ax or whatnot in just that case would not be actually problematic.
> When you and I were discussing a more general feature of distinguishing
> int80 from sysenter from syscall from traps from asynchronous interrupts,
> that was of more concern.
>
> I do feel strongly that any new means of exposing bona fide user state
> ought to be done via the user_regset mechanism. (i.e., either overloading
> some existing user_regs_struct bits if that truly is harmless to
> compatibility, or adding a new regset flavor.) That way it is
> automatically recorded in core files, accessible with PTRACE_GETREGSET,
> etc. (But I'm not really working on this stuff any more, so I'm out of the
> business of arguing strenuously about such opinions.)
>

I think we can obviously agree that regsets is the only way to go for
any kind of new state.

-hpa



\
 
 \ /
  Last update: 2012-01-18 22:59    [W:0.256 / U:0.260 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site