From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86: fix vcpu->mmio_fragments overflow
Date: Mon, 22 Oct 2012 17:36:36 +0200 [thread overview]
Message-ID: <50856804.5030408@redhat.com> (raw)
In-Reply-To: <20121022140056.GY29310@redhat.com>
On 10/22/2012 04:00 PM, Gleb Natapov wrote:
> Yes, with frame buffer is seems to be the case. One can imagine ROMD
> device that is MMIO on write but still can be accessed for read from
> kernel, but it cannot be coalesced even if coalesced buffer is flushed
> on every exit.
You cannot enable coalescing on such a device.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-10-22 15:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 7:37 [PATCH] KVM: x86: fix vcpu->mmio_fragments overflow Xiao Guangrong
2012-10-19 7:39 ` [PATCH] emulator test: add "rep ins" mmio access test Xiao Guangrong
2012-11-01 0:05 ` Marcelo Tosatti
2012-10-22 9:16 ` [PATCH] KVM: x86: fix vcpu->mmio_fragments overflow Gleb Natapov
2012-10-22 11:09 ` Xiao Guangrong
2012-10-22 11:23 ` Gleb Natapov
2012-10-22 11:35 ` Jan Kiszka
2012-10-22 11:43 ` Gleb Natapov
2012-10-22 11:45 ` Jan Kiszka
2012-10-22 12:18 ` Avi Kivity
2012-10-22 12:45 ` Jan Kiszka
2012-10-22 12:53 ` Gleb Natapov
2012-10-22 12:55 ` Jan Kiszka
2012-10-22 12:58 ` Avi Kivity
2012-10-22 13:05 ` Jan Kiszka
2012-10-22 13:08 ` Gleb Natapov
2012-10-22 13:25 ` Jan Kiszka
2012-10-22 14:00 ` Gleb Natapov
2012-10-22 14:23 ` Jan Kiszka
2012-10-22 15:36 ` Avi Kivity [this message]
2012-10-22 12:58 ` Gleb Natapov
2012-10-22 12:55 ` Avi Kivity
2012-10-22 13:01 ` Gleb Natapov
2012-10-22 13:02 ` Avi Kivity
2012-10-22 13:05 ` Gleb Natapov
2012-10-22 12:56 ` Avi Kivity
2012-10-22 13:58 ` Avi Kivity
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=50856804.5030408@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).