search for: oprofiled

I am rebasing Fedora rawhide oprofile package to oprofile-0.9.7. The xenoprof patches on http://xenoprof.sourceforge.net/#download look a bit dated. The newest version is for oprofile-0.9.5. I massaged the patch oprofile-0.9.5-xen.patch to apply to oprofile-.0.9.7. Attached is that updated patch. Does this look reasonable? Is there a desire to get this into upstream oprofile? Or should the

Hi , I am getting following error when i try to run xenoprof /usr/local/bin/opcontrol: line 1082: echo: write error: Invalid argument Using 2.6+ OProfile kernel interface. Reading module info. Using log file /var/lib/oprofile/oprofiled.log Daemon started. what is this write error ? Any help is really appreciated. -John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi , I am getting following error when i try to run xenoprof /usr/local/bin/opcontrol: line 1082: echo: write error: Invalid argument Using 2.6+ OProfile kernel interface. Reading module info. Using log file /var/lib/oprofile/oprofiled.log Daemon started. what is this write error ? Any help is really appreciated. -John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I've been trying to get oprofile results for jitted code without success. I built an 3.5.0 llvm with oprofile enabled, and tested it with lli on a small test case. I built the latest oprofile from the git repository. Debugging I can see that lli is registering the listener and making the oprofile calls to the libopagent api to specify the names and address ranges of jit'd routines, and

Mi Maurice, A follow up to Andy's comments: MCJIT can find line numbers for ELF files, at least in limited circumstances. I know because I broke the regression test for it while doing some cleanup recently. ;) Looking at lib/ExecutionEngine/OProfileJIT/OProfileJITEventListener.cpp, I see the line: // TODO: support line number info (similar to IntelJITEventListener.cpp) >From a glance at

These patches address issues in the kernel part of xenoprof: * Ill-advised use of on_each_cpu() can lead to sleep with interrupts disabled. * Race conditions in active_domains code. * Cleanup of active_domains code. Comments welcome. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Keir, The following 3 patches allow HVM (SVM and VT) guests to be passively profiled using the very latest patches from Renato. These patches apply to 11470. Renato''s patches: http://xenoprof/sourceforge.net oprofile-0.9.1-xen-r2.patch And also a patch not posted FAIK (oprofile-0.9.1-fix-hvm-addr-overlap.patch) which is in the attached tar.bz2 file. hvm_xenoprofile_1.patch - The first

Nicolas Thierry-Mieg, We followed your instructions to yum install oprofile-gui. We were able to install oprofile-guii.i386 0:0.9.4-15.el5.centos and oprofile.i386 0.0.9.4.15.el.5.centos. I was wondering what our next step should be. I tried ./configure --with-kernel-support with oprofile-0.9.6 and obtain a warning, a working QT not found, no GUI was built. Should we try to build

Hi Renato, This patch is to add Xenoprof passive domain support in SMP environment. Basically: - It allocates per vcpu buffers for passive domain and maps them into primary domain''s space. - When primary domain gets sampled and triggers virq, its kernel module will handle passive domain'' samples besides its owns. There is potential buffer overflow if passive is very busy while

Hi I am using oprofile 0.9.3 on xen cs 16540 on an Intel system. When I look at the top "hot" functions, I see p2m_change_type being one of the top function in xen-syms. This function is only in the svm (AMD) code and should not appear on an Intel system. I see that this function is not being clled at all when I am running my apps as I have put printk in the functions and they do

CentOS Errata and Enhancement Advisory 2014:1918 Upstream details at : https://rhn.redhat.com/errata/RHEA-2014-1918.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0f0c9183544e6f82486346105c34a54afcd715514e13cc2ce28069102d32b057 oprofile-0.9.9-6.el6_6.i686.rpm

...rt-daemon --active-domains=41,42 5.) On domU, 41 Opcontrol --reset Opcontrol --start Error: Using default event: CPU_CLK_UNHALTED:100000:0:1:1 Using 2.6+ OProfile kernel interface. Reading module info. Failed to open profile device: Operation not permitted Couldn''t start oprofiled. Check the log file "/var/lib/oprofile/oprofiled.log" and kernel syslog 6.) On domU, 42 Opcontrol --reset Opcontrol --start Error: Using default event: CPU_CLK_UNHALTED:100000:0:1:1 Using 2.6+ OProfile kernel interface. Reading module info. Failed to open profile...

Renato, When I tried running "opcontrol --start" (after previously running "opcontrol --start-daemon") in dom0, I get this error message: /usr/local/bin/opcontrol: line 1639: echo: write error: Operation not permitted and this message in the Xen console: (XEN) xenoprof: operation 9 failed for dom 0 (status : -1) It looks like opcontrol is trying to do this: echo 1 >

Renato, When I tried running "opcontrol --start" (after previously running "opcontrol --start-daemon") in dom0, I get this error message: /usr/local/bin/opcontrol: line 1639: echo: write error: Operation not permitted and this message in the Xen console: (XEN) xenoprof: operation 9 failed for dom 0 (status : -1) It looks like opcontrol is trying to do this: echo 1 >

CentOS Errata and Bugfix Advisory 2018:2443 Upstream details at : https://access.redhat.com/errata/RHBA-2018:2443 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 1f2093e41f3f0283bb7c3d198f3d116d21b6930b8675becbd33c65fa694760f6 oprofile-0.9.9-25.el7_5.1.x86_64.rpm

my system configuration xen 3.4.2, oprofile 0.9.5( xenoprof patched ), dom0( jeremy''s pvops kernel 2.6.31.6 - patched dullor''s xenoprof patch ), domU( vanilla kernel 2.6.32 with paravirt enabled ), distribution( ubuntu 9.10 ) In passive mode, xenoprof seems to work well, opreport showed good information. but, in active mode, it seems not to be done correctly. my command is

The attached patch fixes a Xen panic when a domain is shutdown before oprofile is stopped. Without this patch, free_xenoprof_pages() is called before the domain is destroyed and that, in turn, prevents oprofile from cleaning up pages shared with guests. Shutting down a domain without terminating oprofile therefore causes a Xen panic at a later point in time. The patch was generated against Xen

Hi I am trying to use oprofile with centos 6.0. I know that the debug-info for the kernel is not available, so I believe I used the correct switches to account for this. here is my script... # reset everything opcontrol --shutdown rm /root/.oprofile/da* opcontrol --separate=kernel --no-vmlinux opcontrol --event=CPU_CLK_UNHALTED:100000 opcontrol --start sleep 5

Thanks for the info. I am using old JIT. So that should not be a problem. I will take a look at using oprofile. I have never used it - so will be somewhat of a learning curve. I notice that the configure script has a --with-oprofile option. In addition to enabling that, is there something else that also needs to be done? My copy of LLVM is compiled with --enable-optimized. Will --with-oprofile

...ed the daemon on Dom0 opcontrol --start-daemon --active-domains=1 --separate=library --event=LLC_MISSES:90000 and received the following error: /usr/local/bin/opcontrol: line 1171: echo write error: invalid arguments Using 2.6+ OProfile kernel interface. Using log file /var/lib/oprofile/samples/oprofiled.log Daemon started. Actually, I am able to monitor one event. Then, to monitor another event I do shutdown of daemon and opcontrol. Afterwards, I could not start opcontrol any more on DomU. Maybe the aforementioned error causes that? Do you have any ideas about that? Configuration of the cloud...