lkml.org 
[lkml]   [2006]   [Jun]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH -mm] i386 syscall opcode reordering (pipelining)
Date
Followup to:  <448F1B97.3070207@linux.intel.com>
By author: Arjan van de Ven <arjan@linux.intel.com>
In newsgroup: linux.dev.kernel
>
> Andreas Mohr wrote:
> > Hi all,
> >
> > I'd guess that this version features improved pipeline parallelism,
> > since we isolate competing %ebx accesses (_syscall4()) and
> > stack push operations (_syscall5()), right?
>
> is anybody actually EVER using those???
> I would think not....

Probably not. The _syscallN() macros are broken for the general case
on any 32-bit architecture, since they can't handle multiregister
arguments.

Similarly, a general syscall() function is broken (in the sense that
one would have to have syscall-specific code to mangle the arguments)
on *some*, but not all, 32-bit architectures, since some architectures
have alignment constraints on multiregister arguments, and the syscall
number argument throws off that alignment.

-hpa

-
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/

\
 
 \ /
  Last update: 2006-06-14 00:14    [W:0.037 / U:4.940 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site