This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] xenoprof problems in (xen4.0.1)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xenoprof problems in (xen4.0.1)
From: Yuto Nakai <yuto.k2c@xxxxxxxxx>
Date: Thu, 6 Jan 2011 14:24:58 +0900
Delivery-date: Tue, 11 Jan 2011 02:21:37 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=vRmoLVQON55eGvcMC0fHVH8C3f5HM001jKRoVV96kVo=; b=rd75roEnnmBePYrgQLDvcHasTX4klofyEwn0xk4/8gSS8mqfUvUnL+BY4Dv2DWAqRy 0rJgdhHDtkAGSeLW9l8toraOzy/GW3kxxrE1xg312PBLLvQfDOtwoTOFqCONy3G4ikMR vtuHuhsvFrnT4RsDPBxq4dDg+BdPxg41pSgwk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=HFP3H9zgcsBIUK/PcnRW4Ot68NojJtJaGKWv3ihlKXaDocVqyKvI5R88eeZBN37rcs qLTgVYcMl5EJHLMzgGy2/K94xDkD9xR+oEN3z02Ej632dqQ3MfzJJXAw+4kmCbzxF8vQ Z50pkqp1rlWh29vfhjwJgnQGQZJwGVmYvyGp8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I want to use xenoprof to profile the overhead of the hypervisor.
I patched the oprofile-0.9.5 using the patch from xenoprof.sourceforge.net

Debian GNU/Linux 5.0 (lenny)
Xen-4.0.1 + (linux-2.6-pvops.git) Dom0
My platform is Intel(R) Core(TM) i7 CPU � � � � � 960 �@ 3.20GHz

My problems are:
In Dom0, �after initialization (opcontrol --init), When I start daemon this in Dom0, I got the following error messages :
opcontrol --start-daemon --event=CPU_CLK_UNHALTED:1000000 --xen=/boot/xen-syms-4.0.1

Error: counter 0 not available nmi_watchdog using this resource ? Try: [Comments: there is not /dev/oprofile/0 in /dev/oprofile]

opcontrol --deinit

echo 0 > /proc/sys/kernel/nmi_watchdog �[Comments: I do it using this instructions, but it does not work; and I find that the /proc/sys/kernel/nmi_whatchdog is 0 already]

My questions are:
� �1. Couldn't xenoprof works in Xen 4.0.1 ?

� �2. Why these error message were output If xenoprof works in Xen 4.0.1 ?
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>