From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xen-devel@lists.xensource.com,
"<stefano.stabellini@eu.citrix.com>"
<stefano.stabellini@eu.citrix.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org, anthony.perard@citrix.com
Subject: Re: [Qemu-devel] [Xen-devel] Re: [PATCH] xen: avoid tracking the region 0xa0000 - 0xbffff
Date: Tue, 14 Jun 2011 19:47:37 +0300 [thread overview]
Message-ID: <4DF790A9.4020408@redhat.com> (raw)
In-Reply-To: <4DF7403E.6000503@siemens.com>
On 06/14/2011 02:04 PM, Jan Kiszka wrote:
> BTW, if Xen is not able to track more than one dirty region, I think
> it's time to fix that limitation. At some point it may no longer be
> possible to work around it (who knows how the new memory API will look
> like in this regard).
>
Since the memory API eventually passes its decisions to the accelerator
(tcg/kvm/xen) it shouldn't be a problem to make the decision there as to
which region actually gets logged.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-14 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 15:56 [Qemu-devel] [PATCH] xen: avoid tracking the region 0xa0000 - 0xbffff stefano.stabellini
2011-06-03 15:56 ` [Qemu-devel] [PATCH] cirrus_vga: reset lfb_addr after a pci config write if the BAR is unmapped stefano.stabellini
2011-06-14 13:54 ` Alexander Graf
2011-06-14 16:25 ` Jan Kiszka
[not found] ` <D4463EE3-B9CE-45ED-9371-F2D3E3507898@suse.de>
2011-06-14 11:04 ` [Qemu-devel] [PATCH] xen: avoid tracking the region 0xa0000 - 0xbffff Jan Kiszka
2011-06-14 11:50 ` Stefano Stabellini
2011-06-14 11:59 ` Jan Kiszka
2011-06-14 16:47 ` Avi Kivity [this message]
2011-06-14 11:48 ` Stefano Stabellini
2011-06-14 11:52 ` Alexander Graf
2011-06-14 15:24 ` Stefano Stabellini
2011-06-14 15:24 ` Alexander Graf
2011-06-15 8:09 ` Alexander Graf
2011-06-15 16:27 ` Stefano Stabellini
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=4DF790A9.4020408@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=anthony.perard@citrix.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).