From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Re: UML-patches to prepare UML/s390
Date: Thu, 07 Apr 2005 11:54:16 +0200 [thread overview]
Message-ID: <42550348.1070309@fujitsu-siemens.com> (raw)
In-Reply-To: <200504062150.36496.blaisorblade@yahoo.it>
Blaisorblade wrote:
> On Wednesday 06 April 2005 21:26, Bodo Stroesser wrote:
>>Currently they are the same for 2.4 and 2.6, but worst case that might
>>change in future versions.
>
> Yes maybe in principle, however the errno values are part of the ABI.
I agree.
>
>>Only debugger could note this, as ERESTART_XXXX
>>is unvisible to user programs.
>
> Well, the debugger is a user program, so even this one, which is almost
> internal, is part of the ABI.
I agree.
> #ifndef ERESTARTNOINTR
> #define ERESTARTNOINTR KERN_ERESTARTNOINTR
> #endif
This is the solution, I like.
Here is, what strace programmers do, to decode ERESTARTXXXXX
results (from syscall.c):
... snip ...
#include <errno.h>
... snip ...
#ifdef LINUX
#ifndef ERESTARTSYS
#define ERESTARTSYS 512
#endif
#ifndef ERESTARTNOINTR
#define ERESTARTNOINTR 513
#endif
#ifndef ERESTARTNOHAND
#define ERESTARTNOHAND 514 /* restart if no handler.. */
#endif
#ifndef ENOIOCTLCMD
#define ENOIOCTLCMD 515 /* No ioctl command */
#endif
#ifndef ERESTART_RESTARTBLOCK
#define ERESTART_RESTARTBLOCK 516 /* restart by calling sys_restart_syscall */
#endif
#ifndef NSIG
#define NSIG 32
#endif
#ifdef ARM
#undef NSIG
#define NSIG 32
#undef NR_SYSCALL_BASE
#define NR_SYSCALL_BASE __NR_SYSCALL_BASE
#endif
#endif /* LINUX */
... snip ...
So, I'll modify my patch as you suggested.
Bodo
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-04-07 9:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 13:27 [uml-devel] UML-patches to prepare UML/s390 Bodo Stroesser
2005-04-06 20:35 ` [uml-devel] " Jeff Dike
2005-04-06 18:57 ` Bodo Stroesser
2005-04-06 19:17 ` Blaisorblade
2005-04-06 19:26 ` Bodo Stroesser
2005-04-06 19:50 ` Blaisorblade
2005-04-07 9:54 ` Bodo Stroesser [this message]
2005-04-06 18:59 ` Bodo Stroesser
2005-04-06 19:16 ` Bastian Blank
2005-04-06 19:28 ` Blaisorblade
2005-04-06 19:33 ` Bodo Stroesser
2005-04-06 20:02 ` Bastian Blank
2005-04-06 20:10 ` Blaisorblade
2005-04-07 9:39 ` Bodo Stroesser
2005-04-07 15:57 ` Bodo Stroesser
2005-04-08 1:22 ` [uml-devel] " Blaisorblade
[not found] ` <42562EC4.7040903@fujitsu-siemens.com>
2005-04-17 17:37 ` Blaisorblade
2005-04-18 10:54 ` Bodo Stroesser
2005-04-19 16:45 ` Blaisorblade
2005-04-26 11:31 ` Bodo Stroesser
2005-04-29 20:50 ` Blaisorblade
2005-04-22 1:32 ` [uml-devel] " Jeff Dike
2005-04-24 14:44 ` Blaisorblade
2005-04-24 16:51 ` Jeff Dike
2005-04-24 18:44 ` Blaisorblade
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=42550348.1070309@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.