From: Ingo Molnar <mingo@elte.hu>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
dwalker@mvista.com
Subject: Re: [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c (take 3)
Date: Mon, 4 Dec 2006 22:58:40 +0100 [thread overview]
Message-ID: <20061204215840.GA23604@elte.hu> (raw)
In-Reply-To: <200612042256.51823.zippel@linux-m68k.org>
* Roman Zippel <zippel@linux-m68k.org> wrote:
> While I'm not against this patch, but on m68k I prefer a 32bit cycle
> type (however it's called), so it doesn't solve the original problem.
i havent changed the cycles_t type - it's still 32-bit. I agree with you
that we dont want to bloat 32-bit arch-level code by artificially
forcing everyone to a 64-bit cycles_t.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
dwalker@mvista.com
Subject: Re: [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c (take 3)
Date: Mon, 4 Dec 2006 22:58:40 +0100 [thread overview]
Message-ID: <20061204215840.GA23604@elte.hu> (raw)
In-Reply-To: <200612042256.51823.zippel@linux-m68k.org>
* Roman Zippel <zippel@linux-m68k.org> wrote:
> While I'm not against this patch, but on m68k I prefer a 32bit cycle
> type (however it's called), so it doesn't solve the original problem.
i havent changed the cycles_t type - it's still 32-bit. I agree with you
that we dont want to bloat 32-bit arch-level code by artificially
forcing everyone to a 64-bit cycles_t.
Ingo
next prev parent reply other threads:[~2006-12-04 21:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 19:52 [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c (take 3) Sergei Shtylyov
2006-11-13 19:52 ` Sergei Shtylyov
2006-12-03 19:33 ` Sergei Shtylyov
2006-12-04 9:51 ` Ingo Molnar
2006-12-04 12:29 ` Sergei Shtylyov
2006-12-04 15:39 ` Ingo Molnar
2006-12-04 16:21 ` Sergei Shtylyov
2006-12-04 16:23 ` Ingo Molnar
2006-12-04 17:09 ` Sergei Shtylyov
2006-12-04 17:09 ` Sergei Shtylyov
2006-12-04 21:56 ` Roman Zippel
2006-12-04 21:56 ` Roman Zippel
2006-12-04 21:58 ` Ingo Molnar [this message]
2006-12-04 21:58 ` Ingo Molnar
2006-12-04 18:04 ` Sergei Shtylyov
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=20061204215840.GA23604@elte.hu \
--to=mingo@elte.hu \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=zippel@linux-m68k.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.