From: Blaisorblade <blaisorblade@yahoo.it>
To: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Cc: 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 03:06:09 +0200 [thread overview]
Message-ID: <200505270306.09425.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050527003843.433BA1AEE88@zion.home.lan>
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.
After a bit of checking, I also verified if they had overriden the value of
HARDIRQ_BITS. Which they haven't (it seems it's defined exactly where
CONFIG_HARDIRQS is not used, i.e. nobody is using the ability to override it
currently).
This was not a very deep investigation, however, so feel free to verify this
better.
--
Paolo Giarrusso, aka Blaisorblade
Skype user "PaoloGiarrusso"
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
next prev parent reply other threads:[~2005-05-27 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 0:38 blaisorblade
2005-05-27 1:06 ` Blaisorblade [this message]
2005-05-27 3:31 ` Paul Mundt
2005-05-28 11:21 ` Blaisorblade
2005-05-27 13:33 ` David Howells
2005-05-28 11:19 ` 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=200505270306.09425.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®