Allow for the possibility that even if modules are enabled
that scsi_wait_scan is only made if SCSI_SCAN_ASYNC is
enabled.
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
drivers/scsi/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/Kco
Allow for the possibility that even if modules are enabled
that scsi_wait_scan is only made if SCSI_SCAN_ASYNC is
enabled.
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
drivers/scsi/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/Kconfig b/drivers
This is the Trec driver, Makefile, header files.
Enable trec in Kernel hacking configuration menu.
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
drivers/Makefile |1 +
drivers/trec/Makefile |5 +
drivers/trec/trec.c
Trec's are initialized early in main.c and then dump
trec's in die(), panic() and do_page_fault().
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/traps.c |5 +
arch/x86_64/mm/fault.c |6 ++
init/main.c|4
kernel/p
Trec is a light weight tracing mechanism that places
trace information into a buffer. The contents of the
buffer is dumped when errors occurs or when enabled
via SYSRQ commands.
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
Documentation/trec.txt
Trec's are initialized early in main.c and then dump
trec's in die(), panic() and do_page_fault().
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
arch/x86_64/kernel/traps.c |5 +
arch/x86_64/mm/fault.c |6 ++
init/main.c|4
kernel/panic.c
Trec is a light weight tracing mechanism that places
trace information into a buffer. The contents of the
buffer is dumped when errors occurs or when enabled
via SYSRQ commands.
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
Documentation/trec.txt | 87
This is the Trec driver, Makefile, header files.
Enable trec in Kernel hacking configuration menu.
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
drivers/Makefile |1 +
drivers/trec/Makefile |5 +
drivers/trec/trec.c| 404
On 3/21/07, Johannes Weiner <[EMAIL PROTECTED]> wrote:
Hi,
On Wed, Mar 21, 2007 at 09:49:12AM -0700, Wink Saville wrote:
> >>Please don't use camel-case - in general.
> >>
> Would p_next, p_cur and p_end be OK?
I think it's generally disliked. Quoting Documentati
Johannes Weiner wrote:
Your patch has broken lines where there shouldn't be any.
OK.
+ struct trec_buffer_struct * pNext;
+ struct trec_struct *pCur;
+ struct trec_struct *pEnd;
Please don't use camel-case - in general.
Would p_next,
Johannes Weiner wrote:
Your patch has broken lines where there shouldn't be any.
OK.
+ struct trec_buffer_struct * pNext;
+ struct trec_struct *pCur;
+ struct trec_struct *pEnd;
Please don't use camel-case - in general.
Would p_next,
On 3/21/07, Johannes Weiner [EMAIL PROTECTED] wrote:
Hi,
On Wed, Mar 21, 2007 at 09:49:12AM -0700, Wink Saville wrote:
Please don't use camel-case - in general.
Would p_next, p_cur and p_end be OK?
I think it's generally disliked. Quoting Documentation/CodingStyle:
``Encoding the type
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
kernel/panic.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/kernel/panic.c b/kernel/panic.c
index 623d182..64a047e 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -20,6 +20,10 @@
#include
#i
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
drivers/Kconfig |2 ++
drivers/Makefile |1 +
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/Kconfig b/drivers/Kconfig
index 050323f..f05a2bf 100644
--- a/drivers/Kconfig
+++ b/drivers/Kconfig
@@ -84,4
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
init/main.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/init/main.c b/init/main.c
index a92989e..46bc440 100644
--- a/init/main.c
+++ b/init/main.c
@@ -54,6 +54,7 @@
#include
#include
#include
+#i
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/traps.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/arch/x86_64/kernel/traps.c b/arch/x86_64/kernel/traps.c
index 09d2e8a..c730176 100644
--- a/arch/x86_64/kernel/traps.c
+++
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
arch/x86_64/mm/fault.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/arch/x86_64/mm/fault.c b/arch/x86_64/mm/fault.c
index 6ada723..9857ade 100644
--- a/arch/x86_64/mm/fault.c
+++ b/arch/x86_64/mm/f
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
drivers/trec/Kconfig | 14 ++
drivers/trec/Makefile |5 +
drivers/trec/trec.c| 328
include/asm-generic/trec.h | 17 +++
include/asm-i386/trec.h| 33 +
inclu
Signed-off-by: Wink Saville <[EMAIL PROTECTED]>
---
Documentation/trec.txt | 87
1 files changed, 87 insertions(+), 0 deletions(-)
create mode 100644 Documentation/trec.txt
diff --git a/Documentation/trec.txt b/Documentation/trec.txt
ne
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
Documentation/trec.txt | 87
1 files changed, 87 insertions(+), 0 deletions(-)
create mode 100644 Documentation/trec.txt
diff --git a/Documentation/trec.txt b/Documentation/trec.txt
new file mode
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
drivers/trec/Kconfig | 14 ++
drivers/trec/Makefile |5 +
drivers/trec/trec.c| 328
include/asm-generic/trec.h | 17 +++
include/asm-i386/trec.h| 33 +
include/asm
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
drivers/Kconfig |2 ++
drivers/Makefile |1 +
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/Kconfig b/drivers/Kconfig
index 050323f..f05a2bf 100644
--- a/drivers/Kconfig
+++ b/drivers/Kconfig
@@ -84,4 +84,6
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
init/main.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/init/main.c b/init/main.c
index a92989e..46bc440 100644
--- a/init/main.c
+++ b/init/main.c
@@ -54,6 +54,7 @@
#include linux/lockdep.h
#include linux
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
arch/x86_64/kernel/traps.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/arch/x86_64/kernel/traps.c b/arch/x86_64/kernel/traps.c
index 09d2e8a..c730176 100644
--- a/arch/x86_64/kernel/traps.c
+++ b/arch/x86_64
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
arch/x86_64/mm/fault.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/arch/x86_64/mm/fault.c b/arch/x86_64/mm/fault.c
index 6ada723..9857ade 100644
--- a/arch/x86_64/mm/fault.c
+++ b/arch/x86_64/mm/fault.c
Signed-off-by: Wink Saville [EMAIL PROTECTED]
---
kernel/panic.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/kernel/panic.c b/kernel/panic.c
index 623d182..64a047e 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -20,6 +20,10 @@
#include linux/kexec.h
On 1/22/07, Alan <[EMAIL PROTECTED]> wrote:
> This is accomplished by allocating a page (or more) of memory which
> is executable and mapped into every threads address space. Also, all
> ISR entry points are modified to detect if the code that was interrupted
> was executing within the ACE page.
asynchronous messaging for 4+ years and have found that
it provides very interesting properties, but is hindered because it is not
directly supported by operating systems. I am very interested in getting
feedback on the idea of including asynchronous messaging within the kernel.
Thank you,
Wink Saville
asynchronous messaging for 4+ years and have found that
it provides very interesting properties, but is hindered because it is not
directly supported by operating systems. I am very interested in getting
feedback on the idea of including asynchronous messaging within the kernel.
Thank you,
Wink Saville
On 1/22/07, Alan [EMAIL PROTECTED] wrote:
This is accomplished by allocating a page (or more) of memory which
is executable and mapped into every threads address space. Also, all
ISR entry points are modified to detect if the code that was interrupted
was executing within the ACE page. If it
Arjan van de Ven wrote:
just to make sure, you do realize that when you write "ticks" that rdtsc
doesn't measure cpu clock ticks or cpu cycles anymore, right? (At least
not on your machine)
Yes, that's why I wrote ticks and not cycles. At this point I'm not sure how to
convert
ticks to time
Arjan van de Ven wrote:
just to make sure, you do realize that when you write ticks that rdtsc
doesn't measure cpu clock ticks or cpu cycles anymore, right? (At least
not on your machine)
Yes, that's why I wrote ticks and not cycles. At this point I'm not sure how to
convert
ticks to time
Arjan van de Ven wrote:
it's the cost of a syscall (1000 cycles?) plus what it takes to get a
reasonable time estimate. Assuming your kernel has enough time support
AND your tsc is reasonably ok, it'll be using that. If it's NOT using
that then that's a pretty good sign that you can't also use
Robert Hancock wrote:
Actually, we need to ask the CPU/System makers to provide a system wide
Generally user mode code should just be using gettimeofday. When the TSC
is usable as a sane time source, the kernel will use it. When it's not,
it will use something else like the HPET, ACPI PM Timer
Robert Hancock wrote:
Actually, we need to ask the CPU/System makers to provide a system wide
Generally user mode code should just be using gettimeofday. When the TSC
is usable as a sane time source, the kernel will use it. When it's not,
it will use something else like the HPET, ACPI PM Timer
Arjan van de Ven wrote:
it's the cost of a syscall (1000 cycles?) plus what it takes to get a
reasonable time estimate. Assuming your kernel has enough time support
AND your tsc is reasonably ok, it'll be using that. If it's NOT using
that then that's a pretty good sign that you can't also use
36 matches
Mail list logo
