Re: SATA-performance: Linux vs. FreeBSD

On 02/12/07 08:37, Martin A. Fink wrote: > :~> strace -c -T -o trace.out dd if=/dev/zero of=test.txt bs=10MB count=200 > > 200+0 Datensätze ein > 200+0 Datensätze aus > 20 bytes (2,0 GB) copied, 52,8632 seconds, 37,8 MB/s You might want to check the raw write & read speed to the device w

Re: Need help in understanding x86 syscall

On 08/11/2005 10:18 AM, Steven Rostedt wrote: > It's vanilla 2.6.12-rc3 + Ingo's RT V0.7.46-02-rs-0.4 + some of my own > customizations. But I never touched the sysentry stuff and with a few > printks I see it is being initialized. > >>Also glibc support. > > I'm using Debian unstable with a re

Re: A correct method to use the x86 breakpoint registers (DR0-7)

ce CONFIG_KPROBE off when you have kdb enabled or you get duplicate do_int3() functions defined in arch/i386/traps.c On 07/05/2005 09:20 AM, Jeff Carr wrote: > I'm trying to set the x86 breakpoint registers to trip on write data. > > After they are set, nothing seems to happen when

kprobe support for memory access watchpoints

I was wondering if there are plans to support a method to register watchpoints for memory data access with kprobe. On x86, it's possible to watch for read/write access to arbitrary memory locations via DR memory registers. Perhaps register_kprobe() could be modified to support this or perhaps some

A correct method to use the x86 breakpoint registers (DR0-7)

I'm trying to set the x86 breakpoint registers to trip on write data. After they are set, nothing seems to happen when I trigger them. It's possible I'm not setting them correctly, I tried putting the virt_to_phys() value in them. And, I tried looking at what KPROBE puts in them, but it looks lik