From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Ingo Molnar <mingo@elte.hu>
Cc: Parag Warudkar <kernel-stuff@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: RT patch breaks X86_64 build
Date: Thu, 02 Jun 2005 14:28:22 +0200 [thread overview]
Message-ID: <429EFB66.8030909@stud.feec.vutbr.cz> (raw)
In-Reply-To: <20050601091344.GB11703@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
Ingo Molnar wrote:
> indeed it was broken - i fixed x64 LATENCY_TRACE in the -47-16 kernel.
There's a minor bug in it. Syscalls are numbered from zero, so there's
__NR_syscall_max + 1 of them. Patch attached.
Nonetheless the latency tracing still doesn't work for me on x86_64. It
compiles but hotplug starts to segfault in an infinite loop during
booting up. When I disable CONFIG_LATENCY_TRACE, it works.
Michal
[-- Attachment #2: rt-latency-NR_syscalls.diff --]
[-- Type: text/plain, Size: 378 bytes --]
--- linux-RT.mich/kernel/latency.c.orig 2005-06-02 14:16:12.000000000 +0200
+++ linux-RT.mich/kernel/latency.c 2005-06-02 14:15:37.000000000 +0200
@@ -850,7 +850,7 @@ static int notrace l_show_cmdline(struct
}
#ifdef CONFIG_X86_64
-# define NR_syscalls __NR_syscall_max
+# define NR_syscalls (__NR_syscall_max+1)
#endif
extern unsigned long sys_call_table[NR_syscalls];
next prev parent reply other threads:[~2005-06-02 12:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 1:41 RT patch breaks X86_64 build Parag Warudkar
2005-05-31 2:01 ` Parag Warudkar
2005-05-31 6:08 ` Michal Schmidt
2005-05-31 11:53 ` Parag Warudkar
2005-05-31 12:05 ` Michal Schmidt
2005-06-01 9:13 ` Ingo Molnar
2005-06-02 12:28 ` Michal Schmidt [this message]
2005-06-02 12:39 ` Ingo Molnar
2005-06-02 14:13 ` Michal Schmidt
2005-06-02 15:55 ` Michal Schmidt
2005-06-02 16:17 ` Ingo Molnar
2005-06-02 16:37 ` Michal Schmidt
2005-06-02 18:04 ` Michal Schmidt
2005-06-02 18:33 ` Ingo Molnar
2005-06-02 22:45 ` Michal Schmidt
2005-06-03 5:18 ` Ingo Molnar
2005-06-03 11:03 ` Michal Schmidt
2005-06-02 12:31 ` Michal Schmidt
2005-06-02 12:37 ` Ingo Molnar
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=429EFB66.8030909@stud.feec.vutbr.cz \
--to=xschmi00@stud.feec.vutbr.cz \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.