All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net,
	linuxsh-shmedia-dev@lists.sourceforge.net, linux-sh@m17n.org,
	dhowells@redhat.com
Subject: Re: [patch 4/8] irq code: Add coherence test for PREEMPT_ACTIVE
Date: Fri, 27 May 2005 06:31:26 +0300	[thread overview]
Message-ID: <20050527033126.GH1329@linux-sh.org> (raw)
In-Reply-To: <200505270306.09425.blaisorblade@yahoo.it>

[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]

On Fri, May 27, 2005 at 03:06:09AM +0200, Blaisorblade wrote:
> On Friday 27 May 2005 02:38, blaisorblade@yahoo.it wrote:
> > After porting this fixlet to UML:
> >
> > http://linux.bkbits.net:8080/linux-2.5/cset@41791ab52lfMuF2i3V-eTIGRBbDYKQ
> >
> > , I've also added a warning which should refuse compilation with insane
> > values for PREEMPT_ACTIVE... maybe we should simply move PREEMPT_ACTIVE out
> > of architectures using GENERIC_IRQS.
> Ok, a grep shows that possible culprits (i.e. giving success to
> grep GENERIC_HARDIRQS arch/*/Kconfig, and using 0x4000000 as PREEMPT_ACTIVE, 
> as given by grep PREEMPT_ACTIVE include/asm-*/thread_info.h) are (at a first 
> glance): frv, sh, sh64.
> 
Yeah, that's bogus for sh and sh64 anyways, this should do it.

It would be nice to move PRREMPT_ACTIVE so it isn't per-arch anymore,
there's not many users that use a different value (at least for the ones
using generic hardirqs, ia64 seems to be the only one?).

Signed-off-by: Paul Mundt <lethal@linux-sh.org>

include/asm-sh/thread_info.h: needs update
include/asm-sh64/thread_info.h: needs update
Index: include/asm-sh/thread_info.h
===================================================================
--- 3ac9a34948049bff79a2b2ce49c0a3c84e35a748/include/asm-sh/thread_info.h  (mode:100644)
+++ uncommitted/include/asm-sh/thread_info.h  (mode:100644)
@@ -27,7 +27,7 @@
 
 #endif
 
-#define PREEMPT_ACTIVE		0x4000000
+#define PREEMPT_ACTIVE		0x10000000
 
 /*
  * macros/functions for gaining access to the thread information structure
Index: include/asm-sh64/thread_info.h
===================================================================
--- 3ac9a34948049bff79a2b2ce49c0a3c84e35a748/include/asm-sh64/thread_info.h  (mode:100644)
+++ uncommitted/include/asm-sh64/thread_info.h  (mode:100644)
@@ -73,7 +73,7 @@
 
 #define THREAD_SIZE  8192
 
-#define PREEMPT_ACTIVE		0x4000000
+#define PREEMPT_ACTIVE		0x10000000
 
 /* thread information flags */
 #define TIF_SYSCALL_TRACE	0	/* syscall trace active */

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net,
	linuxsh-shmedia-dev@lists.sourceforge.net, linux-sh@m17n.org,
	dhowells@redhat.com
Subject: [uml-devel] Re: [patch 4/8] irq code: Add coherence test for PREEMPT_ACTIVE
Date: Fri, 27 May 2005 06:31:26 +0300	[thread overview]
Message-ID: <20050527033126.GH1329@linux-sh.org> (raw)
In-Reply-To: <200505270306.09425.blaisorblade@yahoo.it>

[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]

On Fri, May 27, 2005 at 03:06:09AM +0200, Blaisorblade wrote:
> On Friday 27 May 2005 02:38, blaisorblade@yahoo.it wrote:
> > After porting this fixlet to UML:
> >
> > http://linux.bkbits.net:8080/linux-2.5/cset@41791ab52lfMuF2i3V-eTIGRBbDYKQ
> >
> > , I've also added a warning which should refuse compilation with insane
> > values for PREEMPT_ACTIVE... maybe we should simply move PREEMPT_ACTIVE out
> > of architectures using GENERIC_IRQS.
> Ok, a grep shows that possible culprits (i.e. giving success to
> grep GENERIC_HARDIRQS arch/*/Kconfig, and using 0x4000000 as PREEMPT_ACTIVE, 
> as given by grep PREEMPT_ACTIVE include/asm-*/thread_info.h) are (at a first 
> glance): frv, sh, sh64.
> 
Yeah, that's bogus for sh and sh64 anyways, this should do it.

It would be nice to move PRREMPT_ACTIVE so it isn't per-arch anymore,
there's not many users that use a different value (at least for the ones
using generic hardirqs, ia64 seems to be the only one?).

Signed-off-by: Paul Mundt <lethal@linux-sh.org>

include/asm-sh/thread_info.h: needs update
include/asm-sh64/thread_info.h: needs update
Index: include/asm-sh/thread_info.h
===================================================================
--- 3ac9a34948049bff79a2b2ce49c0a3c84e35a748/include/asm-sh/thread_info.h  (mode:100644)
+++ uncommitted/include/asm-sh/thread_info.h  (mode:100644)
@@ -27,7 +27,7 @@
 
 #endif
 
-#define PREEMPT_ACTIVE		0x4000000
+#define PREEMPT_ACTIVE		0x10000000
 
 /*
  * macros/functions for gaining access to the thread information structure
Index: include/asm-sh64/thread_info.h
===================================================================
--- 3ac9a34948049bff79a2b2ce49c0a3c84e35a748/include/asm-sh64/thread_info.h  (mode:100644)
+++ uncommitted/include/asm-sh64/thread_info.h  (mode:100644)
@@ -73,7 +73,7 @@
 
 #define THREAD_SIZE  8192
 
-#define PREEMPT_ACTIVE		0x4000000
+#define PREEMPT_ACTIVE		0x10000000
 
 /* thread information flags */
 #define TIF_SYSCALL_TRACE	0	/* syscall trace active */

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-05-27  3:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27  0:38 [uml-devel] [patch 4/8] irq code: Add coherence test for PREEMPT_ACTIVE blaisorblade
2005-05-27  0:38 ` blaisorblade
2005-05-27  1:06 ` Blaisorblade
2005-05-27  1:06   ` [uml-devel] " Blaisorblade
2005-05-27  3:31   ` Paul Mundt [this message]
2005-05-27  3:31     ` Paul Mundt
2005-05-28 11:21     ` Blaisorblade
2005-05-28 11:21       ` [uml-devel] " Blaisorblade
2005-05-27 13:33   ` David Howells
2005-05-27 13:33     ` [uml-devel] " David Howells
2005-05-28 11:19     ` Blaisorblade
2005-05-28 11:19       ` [uml-devel] " 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=20050527033126.GH1329@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@osdl.org \
    --cc=blaisorblade@yahoo.it \
    --cc=dhowells@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@m17n.org \
    --cc=linuxsh-shmedia-dev@lists.sourceforge.net \
    --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.