similar to: qemu -display sdl,gl=on also eats CPU

The DDX eating CPU isn't intrinsically bad. Did you check where perf says the CPU time is going? Could be doing copies/etc. On Mon, Aug 17, 2020 at 12:52 AM Andrew Randrianasulu <randrianasulu at gmail.com> wrote: > > I was testing Ilia's patches for ddx, and while they definitely helped for Xorg itself, > qemu still eats a lot of CPU if launched like this > >

I rebuild mesa with debug symbols, and now top functions using CPU looks like this: CPU: AMD64 family15h, speed 3800 MHz (estimated) Counted CPU_CLK_UNHALTED events (CPU Clocks not Halted) with a unit mask of 0x00 (No unit mask) count 100000 samples % image name symbol name ------------------------------------------------------------------------------- 222978 45.1489

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

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

Hi all, Is anyone using oprofile? I'm getting segfaults from opreport at the moment, and I'm not sure if it is opreport, or just me. In case it is something just plain daft I am doing, here is how it goes: opcontrol --reset opcontrol --setup --no-vmlinux opcontrol --start ... now I run my program, /tmp/myprog ... opcontrol --dump opcontrol --shutdown then I run, opreport -l

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

Hi, I want to get the performance data like documents <<Xenoprofoverview&Networking Performance Analysis>> (http://www.xensource.com/files/xs0106_xenoprof.pdf ). But how can I get the modules'' profile in kernel? Now I use command: Opcontrol --no-vmlinux --separate=kernel,cpu --start-daemon ...run benchmark Opcontrol --sutdown Opreport >list The report shows: CPU:

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

I observed this bug for quite some time, but so far I workarounded it with just setting DRI2 (default) in xorg.conf.d/20-nouveau.conf Now with two GPU i iwsh to use DRI3, so right now it set up like this: cat /etc/X11/xorg.conf.d/20-nouveau.conf Section "Device" Identifier "Card0" Driver "nouveau" Option "PageFlip" "1" #Option

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 >

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

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

(I posted this on xen-users last week, and nobody seemed to know what was up. It is time, I suppose then, to dust off the debugger; I was hoping one of you could point me in the correct direction to begin troubleshooting this.) I''m HVM booting our install-disks (systemimager) here, and I''m spotting some weird performance issues. Our install uses rsync and prints every

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

I'm aware of this issue, and am experiencing it myself. The issue is that drmmode_event_handler takes up more and more CPU time. It seems like some events are being "left behind". I haven't had time to debug it further yet though. I also have DRI3 enabled, but only very rarely do I make use of my secondary GPUs, and I'm pretty sure I've seen the problem happen without

https://bugs.freedesktop.org/show_bug.cgi?id=103897 Bug ID: 103897 Summary: Kernel 4.14 causes high cpu usage, 4.12 was OK Product: xorg Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau

LLVMers, The 2.2 prerelease is now available for testing: http://llvm.org/prereleases/2.2/ If anyone can help test this release, I ask that you do the following: 1) Build llvm and llvm-gcc (or use a binary). You may build release (default) or debug. You may pick llvm-gcc-4.0, llvm-gcc-4.2, or both. 2) Run 'make check'. 3) In llvm-test, run 'make TEST=nightly report'. 4) When

Hiya, Currently running Centos 4.2 x86_64 dist on a dual 3G xeon, 2G ram, scsi setupand everythings been running fine on it for some time. Then at 4am last night something kicked in (have mrtg running monitoring when) and since then its been running a load of about 1.5 (normally around 0.4). CPU usage is Cpu(s): 1.1% us, 0.6% sy, 0.0% ni, 97.9% id, 0.2% wa, 0.1% hi, 0.1%si. Can't see

? ????????? ?? Sunday 16 August 2020 07:20:18 Ilia Mirkin ???????(?): > Well, if it's easy, try the patches I mailed to nouveau@ for the ddx. I applied patches manually (copy-pasted patches failed to apply by git apply, probably whitespace/end of line issues), and now I see in X log (after I left machine to run alone): [ 3584.553] (DB) NOUVEAU(0): PRESENT: Wait for VBlank failed: Invalid