Date: Wed, 1 Sep 2010 13:23:45 +0200 From: =?UTF-8?Q?Marius_N=C3=BCnnerich?= <marius@nuenneri.ch> To: Rui Paulo <rpaulo@freebsd.org> Cc: "current@freebsd.org Current" <current@freebsd.org> Subject: Re: DTrace userland project Message-ID: <AANLkTinxrU=sduKG8FCqa5s5bJz2CWPbw3QLxiNEFO9_@mail.gmail.com> In-Reply-To: <3A9BC6EA-0F7B-4C57-9179-4E5858894955@freebsd.org> References: <236CEF13-3153-4ACA-9C67-B0116FF76EB3@FreeBSD.org> <AANLkTikNgM4OCSREH7P7NncWBKkNMuAqs1B7qq6Po8HL@mail.gmail.com> <3A9BC6EA-0F7B-4C57-9179-4E5858894955@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 1, 2010 at 12:57, Rui Paulo <rpaulo@freebsd.org> wrote: > On 1 Sep 2010, at 11:20, Marius N=C3=BCnnerich wrote: > >> On Wed, Sep 1, 2010 at 00:21, Rui Paulo <rpaulo@freebsd.org> wrote: >>> Hi, >>> The DTrace userland project is near completion and you can start using = parts of it right away (only on FreeBSD HEAD right now). >>> >>> For more information on how to use DTrace with userland, please read: >>> http://wiki.freebsd.org/DTrace/userland >> >> Hi, >> >> I set this up in a VirtualBox with 9-current r212073 amd64, 4-cores, >> amd-v and nested paging enabled. >> I tried >> dtruss /usr/bin/true >> it works but is really slow, it takes ~10s to switch vt. > > This is not really using the new userland dtrace code, but the old one. I= suspect DTrace has a problem running on your system. Can you try a differe= nt VM software or real hardware? I never experienced this problem on VMWare= Fusion. I have no other VM or real hardware available at the moment. >> I tried the pid example as well, if I execute it on ttyv0 I can see lots= of >> kernel trap 12 with interrupts disabled >> messages flying by and inbetween the desired _sleep:entry probes. When >> I execute that script on ttyv1 I obviously don't see the kernel trap >> messages and the machine kindof locks up (no output at all). I can do >> a clean ACPI shutdown though. > > This looks like I race that I haven't fixed yet. Either way, if the VM is= interfering, then it will be hard to find out how to fix this. It is reproducible every time. But I too have no idea how to tackle this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinxrU=sduKG8FCqa5s5bJz2CWPbw3QLxiNEFO9_>