From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qxl: properly handle upright and non-shared surfaces
Date: Tue, 28 Feb 2012 09:29:38 +0100 [thread overview]
Message-ID: <4F4C9072.8040903@redhat.com> (raw)
In-Reply-To: <20120227191337.GM7395@garlic.redhat.com>
>> - dprint(qxl, 1, "%s: stride %d, [%d, %d, %d, %d]\n", __func__,
>> + dprint(qxl, 2, "%s: stride %d, [%d, %d, %d, %d]\n", __func__,
>
> You know 2 is used right now for high frequency stuff, like
> interface_get_command? I think this should be lower. Anyway, not a big
> deal.
/me used '1' for important but infrequent stuff, basically all init ops,
mode switching etc. This can happen quite alot in case you are running
with SDL. Maybe we need not just 1+2 but 1+2+3 levels, with 3 for the
really frequent stuff which will flood the logfiles.
Or even better just turn them all into tracepoints ...
cheers,
Gerd
next prev parent reply other threads:[~2012-02-28 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 10:10 [Qemu-devel] [PATCH] qxl: properly handle upright and non-shared surfaces Gerd Hoffmann
2012-02-27 19:13 ` Alon Levy
2012-02-28 8:29 ` Gerd Hoffmann [this message]
2012-02-28 8:31 ` Alon Levy
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=4F4C9072.8040903@redhat.com \
--to=kraxel@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).