From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35522) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsIdX-0006YI-Uz for qemu-devel@nongnu.org; Thu, 27 Jun 2013 16:17:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UsIdR-0002Z3-3m for qemu-devel@nongnu.org; Thu, 27 Jun 2013 16:17:47 -0400 Received: from mail-lb0-x236.google.com ([2a00:1450:4010:c04::236]:41810) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsIdQ-0002Yl-Sa for qemu-devel@nongnu.org; Thu, 27 Jun 2013 16:17:41 -0400 Received: by mail-lb0-f182.google.com with SMTP id r11so635920lbv.13 for ; Thu, 27 Jun 2013 13:17:39 -0700 (PDT) MIME-Version: 1.0 From: Claudio Fontana Date: Thu, 27 Jun 2013 22:16:59 +0200 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] Monitoring Screen Activity in QEMU/KVM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: anthony@codemonkey.ws Cc: qemu-devel@nongnu.org > Claudio Fontana writes: > > Shehbaz Jaffer wrote: > > > >> I want to determine the amount of screen activity taking place on VGA > >> monitor/ Screen for different applications (eg. playing vlc video, normal > >> typing.) > >> > >> When I do not start the X server, I can easily determine the screen activity > >> by counting the number of pages accessed in the region 0xA0000 - 0xBffff > >> (This is the VGA Monitor region in boot screen). > >> > >> However when I start the X Server, A diffrent set of pages are hit. Could > >> anyone please explain how the VGA Monitor works in QEMU? Or if someone could > >> suggest an alternate solution to determine amount of screen activity while > >> playing diffrent applications? > >> > >> [NOTE : I have already checked for the region where X server pages are > >> mapped using cat /proc/iomem. But pages are not getting written to the > >> "possible" X server mmapped region.] > >> > >> Regards, > > > > If you define "screen activity" = "number of pages accessed in the > > range 0xa0000-0xbffff per unit of time", you could keep your thing > > going by just using the generic "vga" driver in your Xorg > > configuration, and that would keep your model valid I think. > > Pretty sure the vga driver will use VESA interfaces and the VESA BIOS > will use PCI bar mapping. you are thinking of the generic 'vesa' driver: http://cgit.freedesktop.org/xorg/driver/xf86-video-vesa/ There is also a generic 'vga' driver: http://cgit.freedesktop.org/xorg/driver/xf86-video-vga/ That said, I was being semi-serious: an Xorg running on plain vga driver is hardly a realistic use-case. > You could also trap accesses to where the BAR gets mapped on the PCI > device. Far better to just register a DisplayChangeListener though and > let QEMU do the heavy lifting. > > Or use VNC as Richard mentioned elsewhere. > > Regards, > > Anthony Liguori > > > > > Claudio