From: Ingo Molnar <mingo@elte.hu>
To: Andres Salomon <dilinger@debian.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] highres: Do not run the TIMER_SOFTIRQ after switching to highres mode
Date: Mon, 5 Mar 2007 08:52:05 +0100 [thread overview]
Message-ID: <20070305075205.GA19336@elte.hu> (raw)
In-Reply-To: <45EBCBBE.6000001@debian.org>
* Andres Salomon <dilinger@debian.org> wrote:
> >> And an additional request, just to make it explicit that we should
> >> not have any NO_SOFTIRQ callbacks in the tree; BUG out if we
> >> encounter such a thing.
> >
> > please change it to WARN_ON_ONCE()...
> >
> > 'bug out' might mean: 'dead box'/'no resume'/'no bootup'.
>
> Certainly; note that hrtimers.c has quite a few BUG calls which could
> render a box dead, though.
yep, bad habbit from the days when the vga console was always there to
print stuff on.
Ingo
next prev parent reply other threads:[~2007-03-05 8:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 2:52 [PATCH] dynticks: don't unlock spinlock twice Andres Salomon
2007-03-03 9:02 ` Thomas Gleixner
2007-03-04 11:14 ` Andres Salomon
2007-03-04 13:09 ` [PATCH] highres: Do not run the TIMER_SOFTIRQ after switching to highres mode Thomas Gleixner
2007-03-04 13:12 ` Andres Salomon
2007-03-04 13:23 ` Thomas Gleixner
2007-03-05 7:25 ` Ingo Molnar
2007-03-05 7:50 ` Andres Salomon
2007-03-05 7:52 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-05 1:50 [5/6] 2.6.21-rc2: known regressions Adrian Bunk
2007-03-05 23:43 ` Thomas Gleixner
2007-03-05 23:45 ` Linus Torvalds
2007-03-06 0:38 ` Linus Torvalds
2007-03-06 1:02 ` Thomas Gleixner
2007-03-06 1:31 ` Linus Torvalds
2007-03-06 2:18 ` Linus Torvalds
2007-03-06 10:33 ` Michael S. Tsirkin
2007-03-06 10:37 ` Ingo Molnar
2007-03-06 10:46 ` Michael S. Tsirkin
2007-03-06 11:32 ` Ingo Molnar
2007-03-06 16:44 ` Linus Torvalds
2007-03-06 17:29 ` [PATCH] highres: do not run the TIMER_SOFTIRQ after switching to highres mode Thomas Gleixner
2007-03-06 17:41 ` Linus Torvalds
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=20070305075205.GA19336@elte.hu \
--to=mingo@elte.hu \
--cc=dilinger@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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