From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Con Kolivas <kernel@kolivas.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Instrumenting high latency
Date: Mon, 12 Jul 2004 00:00:37 -0700 [thread overview]
Message-ID: <20040712070037.GU21066@holomorphy.com> (raw)
In-Reply-To: <20040711233750.2050c4b1.akpm@osdl.org>
Con Kolivas <kernel@kolivas.org> wrote:
>> The patch appears to require CONFIG_PREEMPT enabled on uniprocessor and is
>> i386 only at the moment.
On Sun, Jul 11, 2004 at 11:37:50PM -0700, Andrew Morton wrote:
> Not sure what you mean by "on uniprocessor"? AFAICT the patch will work
> as-is on uniprocessor and on SMP. Looks like it'll work with
> CONFIG_PREEMPT=n, too, although that would be a slightly bizarre thing to
> do.
> + print_symbol("%s\n",
> + __get_cpu_var(preempt_exit));
> I'll change this to
> print_symbol("%s",
> __get_cpu_var(preempt_exit));
> printk("\n");
> so it doesn't make a mess with CONFIG_KALLSYMS=n.
I'm not 100% sure why UP goes down in flames yet, fscking laptop has no
loggable console. Guess I'd better figure out netconsole or some such.
-- wli
next prev parent reply other threads:[~2004-07-12 7:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 6:29 [PATCH] Instrumenting high latency Con Kolivas
2004-07-12 6:37 ` Andrew Morton
2004-07-12 6:43 ` Con Kolivas
2004-07-12 6:58 ` Andrew Morton
2004-07-12 7:00 ` William Lee Irwin III [this message]
2004-07-12 7:34 ` [PATCH] " Andrew Morton
2004-07-12 8:02 ` William Lee Irwin III
2004-07-12 8:38 ` William Lee Irwin III
2004-07-12 11:31 ` William Lee Irwin III
2004-07-12 14:32 ` William Lee Irwin III
2004-07-12 17:09 ` Martin Josefsson
2004-07-12 8:29 ` Arjan van de Ven
2004-07-12 8:42 ` William Lee Irwin III
2004-07-12 8:47 ` William Lee Irwin III
2004-07-12 10:41 ` Rajput
2004-07-12 10:44 ` William Lee Irwin III
2004-07-12 14:24 ` Martin J. Bligh
2004-07-12 14:27 ` Con Kolivas
2004-07-12 14:33 ` Martin J. Bligh
2004-07-12 14:42 ` Con Kolivas
2004-07-12 14:47 ` Martin J. Bligh
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=20040712070037.GU21066@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.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.