From: Claudio Fontana <claudio.fontana@gmail.com>
To: anthony@codemonkey.ws
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Monitoring Screen Activity in QEMU/KVM
Date: Thu, 27 Jun 2013 22:16:59 +0200 [thread overview]
Message-ID: <CAJuRt+ogU0pyXTYQ_k565kd9URKZpyzzNT_WSTg4wg-qa88YCA@mail.gmail.com> (raw)
> Claudio Fontana <address@hidden> 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
next reply other threads:[~2013-06-27 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 20:16 Claudio Fontana [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-27 14:09 [Qemu-devel] Monitoring Screen Activity in QEMU/KVM Claudio Fontana
2013-06-27 16:31 ` Anthony Liguori
2013-06-26 2:17 Shehbaz Jaffer
2013-06-26 13:06 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJuRt+ogU0pyXTYQ_k565kd9URKZpyzzNT_WSTg4wg-qa88YCA@mail.gmail.com \
--to=claudio.fontana@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).