qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alexander Larsson <alexl@redhat.com>
Cc: Alon Levy <alevy@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qxl: Export "mode" as a property
Date: Tue, 20 Nov 2012 11:53:48 +0100	[thread overview]
Message-ID: <50AB613C.3060200@redhat.com> (raw)
In-Reply-To: <1353407424.2180.44.camel@fatty>

  Hi,

> I know that, but it would be possible to add code to the driver to
> register a version string.

Sure.  Although it is a bit more complex that just a simple string.
With qxl guest drivers moving to kms as we'll have two driver components
then.

> Might be useful for qxl developers, but not very useful to e.g. a
> helpdesk employee trying to solve an issue for a user, as its kinda
> low-level.

Depends on the problem.  $feature not working and qxl seeing the driver
not using the new ops for $feature is helpful.

> Having the version string would be very nice here.

Indeed, being able to match the driver version against a database of
known-buggy versions is nice too.  That will only work for new drivers
which actually report the version though (assuming we go that route).

But there we are again at the level where going through the guest agent
might be a better way.  "rpm -q kernel xorg-x11-drv-qxl" gives you what
you need ...

cheers,
  Gerd

  reply	other threads:[~2012-11-20 10:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 13:11 [Qemu-devel] [PATCH] qxl: Export "mode" as a property Alexander Larsson
2012-11-20  7:50 ` Gerd Hoffmann
2012-11-20  9:07   ` Daniel P. Berrange
2012-11-20  9:15     ` Gerd Hoffmann
2012-11-20  9:35       ` Alexander Larsson
2012-11-20 10:17         ` Gerd Hoffmann
2012-11-20 10:30           ` Alexander Larsson
2012-11-20 10:53             ` Gerd Hoffmann [this message]
2012-11-20 11:41               ` Alexander Larsson
2012-11-20  9:49       ` Alon Levy
2012-11-20  9:48   ` Markus Armbruster
2012-11-20  9:51     ` Alexander Larsson
2012-11-20 10:28     ` Gerd Hoffmann

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=50AB613C.3060200@redhat.com \
    --to=kraxel@redhat.com \
    --cc=alevy@redhat.com \
    --cc=alexl@redhat.com \
    --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).