From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 1/2] Move graphic-related coalesced MMIO flushes to affected device models
Date: Tue, 18 Oct 2011 16:10:17 +0200 [thread overview]
Message-ID: <4E9D88C9.1010804@siemens.com> (raw)
In-Reply-To: <4E9D884B.30309@redhat.com>
On 2011-10-18 16:08, Avi Kivity wrote:
> On 10/18/2011 04:05 PM, Jan Kiszka wrote:
>> On 2011-10-18 16:00, Avi Kivity wrote:
>>> On 09/30/2011 01:31 PM, Jan Kiszka wrote:
>>>> This is conceptually cleaner and will allow us to drop the nographic
>>>> timer. Moreover, it will be mandatory to fully exploit future per-device
>>>> coalesced MMIO rings.
>>>>
>>>
>>> Appears to break winxp installation - the guest enters an infinite
>>> bitblt loop. Trying to find out why.
>>
>> Hmm, maybe there are side effects in certain modes that actually
>> disallow coalescing.
>>
>
> That's true for sure, but flushing the buffer should never be wrong.
Err, you mean we are not flushing "too often"? I was under the
impression winxp is missing our periodic flushes. Do things work again
when you do not flush at all?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-10-18 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 10:31 [Qemu-devel] [PATCH 1/2] Move graphic-related coalesced MMIO flushes to affected device models Jan Kiszka
2011-10-15 21:35 ` Blue Swirl
2011-10-18 14:00 ` Avi Kivity
2011-10-18 14:05 ` Jan Kiszka
2011-10-18 14:08 ` Avi Kivity
2011-10-18 14:10 ` Jan Kiszka [this message]
2011-10-18 14:30 ` Avi Kivity
2011-10-18 16:40 ` Avi Kivity
2011-10-18 16:49 ` Jan Kiszka
2011-10-18 17:34 ` Avi Kivity
2011-10-18 19:50 ` Jan Kiszka
2011-10-19 9:04 ` Avi Kivity
2011-10-19 11:18 ` Jan Kiszka
2011-10-18 18:06 ` 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=4E9D88C9.1010804@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.