From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH] memory: synchronize dirty bitmap before unmapping a range
Date: Mon, 01 Aug 2011 09:34:48 +0200 [thread overview]
Message-ID: <4E365718.2060500@web.de> (raw)
In-Reply-To: <1312141678-5141-1-git-send-email-avi@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On 2011-07-31 21:47, Avi Kivity wrote:
> When a range is being unmapped, ask accelerators (e.g. kvm) to synchronize the
> dirty bitmap to avoid losing information forever.
>
> Fixes grub2 screen update.
I does.
But something is still broken. As I reported before, the performance of
grub2 startup is an order of magnitude slower than with the existing
code. According to ftrace, we are getting tons of additional
EPT_MISCONFIG exits over the 0xA0000 segment. But I haven't spot the
difference yet. The effective slot setup as communicated to kvm looks
innocent.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] memory: synchronize dirty bitmap before unmapping a range
Date: Mon, 01 Aug 2011 09:34:48 +0200 [thread overview]
Message-ID: <4E365718.2060500@web.de> (raw)
In-Reply-To: <1312141678-5141-1-git-send-email-avi@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On 2011-07-31 21:47, Avi Kivity wrote:
> When a range is being unmapped, ask accelerators (e.g. kvm) to synchronize the
> dirty bitmap to avoid losing information forever.
>
> Fixes grub2 screen update.
I does.
But something is still broken. As I reported before, the performance of
grub2 startup is an order of magnitude slower than with the existing
code. According to ftrace, we are getting tons of additional
EPT_MISCONFIG exits over the 0xA0000 segment. But I haven't spot the
difference yet. The effective slot setup as communicated to kvm looks
innocent.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-08-01 7:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 19:47 [PATCH] memory: synchronize dirty bitmap before unmapping a range Avi Kivity
2011-07-31 19:47 ` [Qemu-devel] " Avi Kivity
2011-08-01 7:34 ` Jan Kiszka [this message]
2011-08-01 7:34 ` Jan Kiszka
2011-08-01 7:52 ` Jan Kiszka
2011-08-01 7:52 ` [Qemu-devel] " Jan Kiszka
2011-08-01 8:16 ` Avi Kivity
2011-08-01 8:16 ` [Qemu-devel] " Avi Kivity
2011-08-01 9:05 ` Jan Kiszka
2011-08-01 9:05 ` [Qemu-devel] " Jan Kiszka
2011-08-01 9:30 ` Avi Kivity
2011-08-01 9:30 ` [Qemu-devel] " Avi Kivity
2011-08-01 9:32 ` Avi Kivity
2011-08-01 9:32 ` [Qemu-devel] " Avi Kivity
2011-08-01 9:45 ` Avi Kivity
2011-08-01 9:45 ` [Qemu-devel] " Avi Kivity
2011-08-01 10:21 ` Jan Kiszka
2011-08-01 10:21 ` [Qemu-devel] " Jan Kiszka
2011-08-01 10:27 ` Avi Kivity
2011-08-01 10:27 ` [Qemu-devel] " Avi Kivity
2011-08-05 16:47 ` Anthony Liguori
2011-08-05 16:47 ` Anthony Liguori
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=4E365718.2060500@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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.