Christoph Hellwig wrote:
Your mailer wrapper the patch so I can't actually apply it to start
playing with the patch.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Christoph Hellwig wrote:
Your mailer wrapper the patch so I can't actually apply it to start
playing with the patch.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Your mailer wrapper the patch so I can't actually apply it to start
playing with the patch.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
Your mailer wrapper the patch so I can't actually apply it to start
playing with the patch.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On Fri, 21 Sep 2007 14:48:14 -0700 David J. Wilder wrote:
> I updated the example code to eliminate the use of the temp print buffer
> and the use of NR_CPU.
>
> Please see previous postings for more information and patch
> dependencies.
> http://lkml.org/lkml/2007/9/19/4 (PATCH 0/2)
>
I updated the example code to eliminate the use of the temp print buffer
and the use of NR_CPU.
Please see previous postings for more information and patch
dependencies.
http://lkml.org/lkml/2007/9/19/4 (PATCH 0/2)
http://lkml.org/lkml/2007/9/19/6 (PATCH 2/2)
-
Trace -
I updated the example code to eliminate the use of the temp print buffer
and the use of NR_CPU.
Please see previous postings for more information and patch
dependencies.
http://lkml.org/lkml/2007/9/19/4 (PATCH 0/2)
http://lkml.org/lkml/2007/9/19/6 (PATCH 2/2)
---start of
On Fri, 21 Sep 2007 14:48:14 -0700 David J. Wilder wrote:
I updated the example code to eliminate the use of the temp print buffer
and the use of NR_CPU.
Please see previous postings for more information and patch
dependencies.
http://lkml.org/lkml/2007/9/19/4 (PATCH 0/2)
On Wed, 19 Sep 2007 17:20:18 +0100 Christoph Hellwig wrote:
> On Wed, Sep 19, 2007 at 07:14:47AM -0700, David Wilder wrote:
> > I agree with you; however, this is in the example code in the
> > Documentation directory, It is not part of the trace code. The example
> > was just meant to be a
On Wed, Sep 19, 2007 at 07:48:45PM +0200, Sam Ravnborg wrote:
> > Well, this is kernel code - so util-linux is not the solution here
> > obviously :)
>
> Can you sketch what you have in mind.
> We right now have said we wnated to:
> 1) include a framework for executing simple
On Wed, Sep 19, 2007 at 05:55:07PM +0100, Christoph Hellwig wrote:
> On Wed, Sep 19, 2007 at 09:52:23AM -0700, Randy Dunlap wrote:
> > That's why they exmaples should not be hidden/embedded in .txt files;
> > they should be standalone .c files with makefiles etc.
>
> Yes. And most importantly
Randy Dunlap wrote:
On Wed, 19 Sep 2007 17:20:18 +0100 Christoph Hellwig wrote:
On Wed, Sep 19, 2007 at 07:14:47AM -0700, David Wilder wrote:
I agree with you; however, this is in the example code in the
Documentation directory, It is not part of the trace code. The example
was just meant
On Wed, Sep 19, 2007 at 09:52:23AM -0700, Randy Dunlap wrote:
> That's why they exmaples should not be hidden/embedded in .txt files;
> they should be standalone .c files with makefiles etc.
Yes. And most importantly integrated with the kernel build system.
> and they can be taken out of
On Wed, Sep 19, 2007 at 07:14:47AM -0700, David Wilder wrote:
> I agree with you; however, this is in the example code in the
> Documentation directory, It is not part of the trace code. The example
> was just meant to be a demonstration of how the interface works.
So we tell people to write
> I agree with you; however, this is in the example code in the
> Documentation directory, It is not part of the trace code. The example
> was just meant to be a demonstration of how the interface works.
That's not a good excuse. In fact it's a very bad one.
Especially example code needs to
Andi Kleen wrote:
"David J. Wilder" <[EMAIL PROTECTED]> writes:
Not having read the whole thing; just something I noticed.
Gut feeling is that you have too many knobs and options and
some overengineering though -- simplifying it would be a good thing.
+
+#define TRACE_PRINTF_TMPBUF_SIZE
"David J. Wilder" <[EMAIL PROTECTED]> writes:
Not having read the whole thing; just something I noticed.
Gut feeling is that you have too many knobs and options and
some overengineering though -- simplifying it would be a good thing.
> +
> +#define TRACE_PRINTF_TMPBUF_SIZE (1024)
> +static
David J. Wilder [EMAIL PROTECTED] writes:
Not having read the whole thing; just something I noticed.
Gut feeling is that you have too many knobs and options and
some overengineering though -- simplifying it would be a good thing.
+
+#define TRACE_PRINTF_TMPBUF_SIZE (1024)
+static char
Andi Kleen wrote:
David J. Wilder [EMAIL PROTECTED] writes:
Not having read the whole thing; just something I noticed.
Gut feeling is that you have too many knobs and options and
some overengineering though -- simplifying it would be a good thing.
+
+#define TRACE_PRINTF_TMPBUF_SIZE (1024)
I agree with you; however, this is in the example code in the
Documentation directory, It is not part of the trace code. The example
was just meant to be a demonstration of how the interface works.
That's not a good excuse. In fact it's a very bad one.
Especially example code needs to be
On Wed, Sep 19, 2007 at 07:14:47AM -0700, David Wilder wrote:
I agree with you; however, this is in the example code in the
Documentation directory, It is not part of the trace code. The example
was just meant to be a demonstration of how the interface works.
So we tell people to write bad
On Wed, Sep 19, 2007 at 09:52:23AM -0700, Randy Dunlap wrote:
That's why they exmaples should not be hidden/embedded in .txt files;
they should be standalone .c files with makefiles etc.
Yes. And most importantly integrated with the kernel build system.
and they can be taken out of
Randy Dunlap wrote:
On Wed, 19 Sep 2007 17:20:18 +0100 Christoph Hellwig wrote:
On Wed, Sep 19, 2007 at 07:14:47AM -0700, David Wilder wrote:
I agree with you; however, this is in the example code in the
Documentation directory, It is not part of the trace code. The example
was just meant
On Wed, Sep 19, 2007 at 05:55:07PM +0100, Christoph Hellwig wrote:
On Wed, Sep 19, 2007 at 09:52:23AM -0700, Randy Dunlap wrote:
That's why they exmaples should not be hidden/embedded in .txt files;
they should be standalone .c files with makefiles etc.
Yes. And most importantly
On Wed, Sep 19, 2007 at 07:48:45PM +0200, Sam Ravnborg wrote:
Well, this is kernel code - so util-linux is not the solution here
obviously :)
Can you sketch what you have in mind.
We right now have said we wnated to:
1) include a framework for executing simple new-syscall-test-stubs
2)
On Wed, 19 Sep 2007 17:20:18 +0100 Christoph Hellwig wrote:
On Wed, Sep 19, 2007 at 07:14:47AM -0700, David Wilder wrote:
I agree with you; however, this is in the example code in the
Documentation directory, It is not part of the trace code. The example
was just meant to be a
Trace - Provides tracing primitives
Signed-off-by: Tom Zanussi <[EMAIL PROTECTED]>
Signed-off-by: Martin Hunt <[EMAIL PROTECTED]>
Signed-off-by: David Wilder <[EMAIL PROTECTED]>
---
Documentation/trace/src/Makefile |7 +
Documentation/trace/src/README | 18 +
Trace - Provides tracing primitives
Signed-off-by: Tom Zanussi [EMAIL PROTECTED]
Signed-off-by: Martin Hunt [EMAIL PROTECTED]
Signed-off-by: David Wilder [EMAIL PROTECTED]
---
Documentation/trace/src/Makefile |7 +
Documentation/trace/src/README | 18 +
28 matches
Mail list logo
