From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: Flush coalesced MMIO buffer periodly
Date: Thu, 21 Jan 2010 12:19:49 +0200 [thread overview]
Message-ID: <4B582A45.3020404@redhat.com> (raw)
In-Reply-To: <1264066640-25577-1-git-send-email-sheng@linux.intel.com>
On 01/21/2010 11:37 AM, Sheng Yang wrote:
> The default action of coalesced MMIO is, cache the writing in buffer, until:
> 1. The buffer is full.
> 2. Or the exit to QEmu due to other reasons.
>
> But this would result in a very late writing in some condition.
> 1. The each time write to MMIO content is small.
> 2. The writing interval is big.
> 3. No need for input or accessing other devices frequently.
>
> This issue was observed in a experimental embbed system. The test image
> simply print "test" every 1 seconds. The output in QEmu meets expectation,
> but the output in KVM is delayed for seconds.
>
> Per Avi's suggestion, I add a periodly flushing coalesced MMIO buffer in
> QEmu IO thread. By this way, We don't need vcpu explicit exit to QEmu to
> handle this issue. Current synchronize rate is 1/25s.
>
>
I'm not sure that a new timer is needed. If the only problem case is
the display, maybe we can flush coalesced mmio from the vga refresh
timer. That ensures that we flash exactly when needed, and don't have
extra timers.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-21 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 9:37 [PATCH] kvm: Flush coalesced MMIO buffer periodly Sheng Yang
2010-01-21 10:19 ` Avi Kivity [this message]
2010-01-22 2:22 ` Sheng Yang
2010-01-24 7:35 ` Avi Kivity
2010-01-25 7:45 ` Sheng Yang
-- strict thread matches above, loose matches on Subject: below --
2010-01-25 7:46 Sheng Yang
2010-01-25 16:08 ` Marcelo Tosatti
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=4B582A45.3020404@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.com \
/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