All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: linux-mips@linux-mips.org
Subject: [RFC] Add 4/8 bytes to 'struct k_sigaction'...
Date: Wed, 05 Jan 2005 22:36:08 -0600	[thread overview]
Message-ID: <41DCC038.9000307@realitydiluted.com> (raw)

In order support easy building of IRIX emulation support as either
a module or statically, I would like to simply have the 'sa_restorer'
function pointer be defined for all big endian architectures. This
means extra storage space, but I wanted comments first. The problem
is that if you configure for IRIX, build and then decide that you
want to build it as a module, CONFIG_BINFMT_IRIX_MODULE gets defined
instead of CONFIG_BINFMT_IRIX and hence 'signal.h' changes and the
whole kernel has to be rebuilt. If we simply have it be defined for
big endian architectures regardless, then there is no recompile. Al
Viro did comment that Christoph Hellwig may be moving stuff like
'struct sighand_struct' out of 'sched.h' along with some other things
which might make this below a non-issue, but that is far off. Comments
before I commit?

-Steve

Index: signal.h
===================================================================
RCS file: /home/cvs/linux/include/asm-mips/signal.h,v
retrieving revision 1.17
diff -u -r1.17 signal.h
--- signal.h	30 Sep 2003 14:27:29 -0000	1.17
+++ signal.h	6 Jan 2005 04:21:58 -0000
@@ -135,7 +135,7 @@

  struct k_sigaction {
  	struct sigaction sa;
-#ifdef CONFIG_BINFMT_IRIX
+#if !defined(CONFIG_CPU_LITTLE_ENDIAN)
  	void		(*sa_restorer)(void);
  #endif
  };

             reply	other threads:[~2005-01-06  4:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06  4:36 Steven J. Hill [this message]
2005-01-06 15:48 ` [RFC] Add 4/8 bytes to 'struct k_sigaction' Christoph Hellwig
2005-01-06 15:55   ` sjhill
2005-01-06 16:12   ` Thiemo Seufer

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=41DCC038.9000307@realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=linux-mips@linux-mips.org \
    /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.