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

Update, after few hours of qemu uptime I can see this oreport: 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 % linenr info image name symbol name ------------------------------------------------------------------------------- 385793

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 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 qemu-system-x86_64 -cdrom ~/Downloads/ISO/slax-English-US-7.0.8-x86_64.iso -m 1G -display sdl,gl=on -enable-kvm and left for few hours. top - 07:38:01 up 18:05, 2 users, load average: 2,00, 1,89, 1,83 Tasks: 224 total, 3 running, 221 sleeping, 0

? ????????? ?? 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

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

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

http://bugs.freedesktop.org/show_bug.cgi?id=23086 Summary: TNT2 doesn't start with current nouveau Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hello, I'm using Puppy linux 4.0, kernel 2.6.21.7. Output of ./configure (last lines): configure: libxi development files not found, configure: libxcomposite development files not found, configure: libGLU development files not found, configure: libhal development files not found configure: libldap (OpenLDAP) development files not found configure: libcapi20 development files not found

http://bugs.freedesktop.org/show_bug.cgi?id=13689 Summary: nouveau is much slower than nv with flash player Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

OK, I need to start with a basic "dumb" question. What named xorg version does my package version 1.15 correspond to? X11R7.? Currently, I'm having some bad flicker problems I didn't experience previously. I have an old old radeon graphics card and note that the ati driver was updated with 6.7. This loads for X before the radeon module. I didn't find any release notes

In ubuntu 6,06 the R normally run, but latter to install the a vesion 6,10 plot this not appearing. computer with problem: /usr/share/X11/fonts$ ls misc Type1 X11R7 In computer OK: /usr/share/X11/fonts$ls 100dpi(*) 75dpi encodings fonts.cache-1 misc Type1 ----- Mensagem original ---- De: Peter Dalgaard <p.dalgaard@biostat.ku.dk> Para: Ricardo Arias Brito

https://bugs.freedesktop.org/show_bug.cgi?id=110679 Bug ID: 110679 Summary: va-api scaling with nv50-class cards incomplete? Product: Mesa Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 xtrans is a library of code that is shared (but is *not* a shared library) among various X packages to handle network protocol transport in a modular fashion, allowing a single place to add new transport types. It is used by the X server, libX11, libICE, the X font server, and related components. This minor release converts the libxtrans API

On 08/17/2015 01:55 PM, Kay Schenk wrote: > OK, I need to start with a basic "dumb" question. What named xorg > version does my package version 1.15 correspond to? X11R7.? X11r7.7, I think. http://www.x.org/wiki/Releases/ > Currently, I'm having some bad flicker problems I didn't experience > previously. I have an old old radeon graphics card and note that the ati

http://bugs.freedesktop.org/show_bug.cgi?id=20848 Summary: Nouveau crashes on rotation Product: xorg Version: 7.4 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: luizluca at

The python3 bindings create unicode objects from application strings on the guest (i.e. installed rpm, deb packages). It is documented that rpm package fields such as description should be utf8 encoded - however in some cases they are not a valid unicode string, on SLES11 SP4 the following packages fail to be converted to unicode using guestfs_int_py_fromstring() (which invokes

On Mon, Apr 20, 2020 at 01:17:35PM +0300, Sam Eiderman wrote: > The python3 bindings create unicode objects from application strings > on the guest (i.e. installed rpm, deb packages). > It is documented that rpm package fields such as description should be > utf8 encoded - however in some cases they are not a valid unicode > string, on SLES11 SP4 the following packages fail to be

On Mon, Apr 20, 2020 at 03:37:16PM +0300, Sam Eiderman wrote: > The python3 bindings create unicode objects from application strings > on the guest (i.e. installed rpm, deb packages). > It is documented that rpm package fields such as description should be > utf8 encoded - however in some cases they are not a valid unicode > string, on SLES11 SP4 the following packages fail to be

On Mon, Apr 20, 2020 at 3:38 PM Sam Eiderman <sameid@google.com> wrote: > > The python3 bindings create unicode objects from application strings > on the guest (i.e. installed rpm, deb packages). > It is documented that rpm package fields such as description should be > utf8 encoded - however in some cases they are not a valid unicode > string, So what are they? latin1

On Sun, Apr 26, 2020 at 09:14:03PM +0300, Sam Eiderman wrote: > The python3 bindings create PyUnicode objects from application strings > on the guest (i.e. installed rpm, deb packages). > It is documented that rpm package fields such as description should be > utf8 encoded - however in some cases they are not a valid unicode > string, on SLES11 SP4 the encoding of the description of