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:31:09 +0200 [thread overview]
Message-ID: <429EFC0D.9020703@stud.feec.vutbr.cz> (raw)
In-Reply-To: <20050601091344.GB11703@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 196 bytes --]
Hi Ingo,
I don't see why /proc/sys/kernel/preempt_{max_latency,thresh} should not
be readable for all users. They already can see much more detailed
information in /proc/latency_trace.
Michal
[-- Attachment #2: rt-latency-procfiles.diff --]
[-- Type: text/plain, Size: 734 bytes --]
--- linux-RT.mich/kernel/latency.c.orig 2005-06-02 13:42:23.000000000 +0200
+++ linux-RT.mich/kernel/latency.c 2005-06-02 12:57:05.000000000 +0200
@@ -1809,14 +1809,14 @@ static __init int latency_init(void)
{
struct proc_dir_entry *entry;
- entry = create_proc_entry("sys/kernel/preempt_max_latency", 0600, NULL);
+ entry = create_proc_entry("sys/kernel/preempt_max_latency", 0644, NULL);
entry->nlink = 1;
entry->data = &preempt_max_latency;
entry->read_proc = preempt_read_proc;
entry->write_proc = preempt_write_proc;
- entry = create_proc_entry("sys/kernel/preempt_thresh", 0600, NULL);
+ entry = create_proc_entry("sys/kernel/preempt_thresh", 0644, NULL);
entry->nlink = 1;
entry->data = &preempt_thresh;
next prev parent reply other threads:[~2005-06-02 12:31 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
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 [this message]
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=429EFC0D.9020703@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.