qemu/linux-user/m68k/target_signal.h

#ifndef M68K_TARGET_SIGNAL_H
#define M68K_TARGET_SIGNAL_H

/* this struct defines a stack used during syscall handling */

typedef struct target_sigaltstack {
    abi_ulong ss_sp;
    abi_int ss_flags;
    abi_ulong ss_size;
} target_stack_t;


/*
 * sigaltstack controls
 */
#define TARGET_SS_ONSTACK	1
#define TARGET_SS_DISABLE	2

#define TARGET_MINSIGSTKSZ	2048
#define TARGET_SIGSTKSZ	8192

#include "../generic/signal.h"

#define TARGET_ARCH_HAS_SETUP_FRAME
#endif /* M68K_TARGET_SIGNAL_H */
linux-user: Clean up target_signal.h header guards These headers all use TARGET_SIGNAL_H as header guard symbol. Reuse of the same guard symbol in multiple headers is okay as long as they cannot be included together. Since we can avoid guard symbol reuse easily, do so: use guard symbol $target_TARGET_SIGNAL_H for linux-user/$target/target_signal.h. Signed-off-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Richard Henderson <rth@twiddle.net> 2016-06-29 17:09:50 +03:00			`#ifndef M68K_TARGET_SIGNAL_H`
			`#define M68K_TARGET_SIGNAL_H`
linux-user sigaltstack() syscall, by Thayne Harbaugh. git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@3252 c046a42c-6fe2-441c-8c8c-71466251a162 2007-09-27 17:57:58 +04:00
			`/* this struct defines a stack used during syscall handling */`

			`typedef struct target_sigaltstack {`
linux-user: Correct definition of stack_t Some platforms used the wrong definition of stack_t where the flags and size fields were swapped or where the flags field had type ulong instead of int. Due to the presence of padding space in the structure and the prevalence of little-endian machines this problem went unnoticed for a long time. The type definitions have been cross-checked with the ones defined in the Linux kernel v5.9, plus some older versions for a few architecture that have been removed and Xilinx's kernel fork for NiosII [1]. The bsd-user headers remain unchanged as I don't know if they are wrong or not. [1] https://github.com/Xilinx/linux-xlnx/blob/master/arch/nios2/include/uapi/asm/signal.h Signed-off-by: Giuseppe Musacchio <thatlemon@gmail.com> Reviewed-by: Peter Maydell <peter.maydell@linaro.org> Message-Id: <e9d47692-ee92-009f-6007-0abc3f502b97@gmail.com> Signed-off-by: Laurent Vivier <laurent@vivier.eu> 2020-11-05 18:52:51 +03:00			`abi_ulong ss_sp;`
			`abi_int ss_flags;`
			`abi_ulong ss_size;`
Revert "Get rid of _t suffix" In the very least, a change like this requires discussion on the list. The naming convention is goofy and it causes a massive merge problem. Something like this _must_ be presented on the list first so people can provide input and cope with it. This reverts commit 99a0949b720a0936da2052cb9a46db04ffc6db29. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> 2009-10-02 01:12:16 +04:00			`} target_stack_t;`
linux-user sigaltstack() syscall, by Thayne Harbaugh. git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@3252 c046a42c-6fe2-441c-8c8c-71466251a162 2007-09-27 17:57:58 +04:00

			`/*`
			`* sigaltstack controls`
			`*/`
			`#define TARGET_SS_ONSTACK 1`
			`#define TARGET_SS_DISABLE 2`

			`#define TARGET_MINSIGSTKSZ 2048`
			`#define TARGET_SIGSTKSZ 8192`

linux-user: move generic signal definitions to generic/signal.h No code change. Signed-off-by: Laurent Vivier <laurent@vivier.eu> Message-Id: <20180529194207.31503-10-laurent@vivier.eu> 2018-05-29 22:42:01 +03:00			`#include "../generic/signal.h"`

linux-user: define TARGET_ARCH_HAS_SETUP_FRAME Instead of calling setup_frame() conditionally to a list of known targets, define TARGET_ARCH_HAS_SETUP_FRAME if the target provides the function and call it only if the macro is defined. Move declarations of setup_frame() and setup_rt_frame() to linux-user/signal-common.h Signed-off-by: Laurent Vivier <laurent@vivier.eu> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Message-Id: <20180424192635.6027-21-laurent@vivier.eu> 2018-04-24 22:26:35 +03:00			`#define TARGET_ARCH_HAS_SETUP_FRAME`
linux-user: Clean up target_signal.h header guards These headers all use TARGET_SIGNAL_H as header guard symbol. Reuse of the same guard symbol in multiple headers is okay as long as they cannot be included together. Since we can avoid guard symbol reuse easily, do so: use guard symbol $target_TARGET_SIGNAL_H for linux-user/$target/target_signal.h. Signed-off-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Richard Henderson <rth@twiddle.net> 2016-06-29 17:09:50 +03:00			`#endif /* M68K_TARGET_SIGNAL_H */`