From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>,
Blue Swirl <blauwirbel@gmail.com>,
ohmura.kei@lab.ntt.co.jp, kvm@vger.kernel.org,
Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 2/6] qemu-kvm: Modify and introduce wrapper functions to access phys_ram_dirty.
Date: Wed, 17 Mar 2010 00:05:03 +0000 [thread overview]
Message-ID: <201003170005.03822.paul@codesourcery.com> (raw)
In-Reply-To: <4BA006DB.3070205@twiddle.net>
> Where does the translator need access to this original code? I was
> just thinking about this problem today, wondering how much overhead
> there is with this SMC page protection thing.
When an MMU fault occurs qemu re-translates the TB with additional annotations
to determine which guest instruction caused the fault.
See translate-all.c:cpu_restore_state().
Paul
next prev parent reply other threads:[~2010-03-17 0:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 10:53 [PATCH 0/6] qemu-kvm: Introduce bit-based phys_ram_dirty, and bit-based dirty page checker Yoshiaki Tamura
2010-03-16 10:53 ` [PATCH 1/6] qemu-kvm: Introduce bit-based phys_ram_dirty for VGA, CODE and MIGRATION Yoshiaki Tamura
2010-03-16 12:26 ` Avi Kivity
2010-03-16 13:01 ` Yoshiaki Tamura
2010-03-16 13:04 ` Avi Kivity
2010-03-16 10:53 ` [PATCH 2/6] qemu-kvm: Modify and introduce wrapper functions to access phys_ram_dirty Yoshiaki Tamura
2010-03-16 12:45 ` Avi Kivity
2010-03-16 13:17 ` Yoshiaki Tamura
2010-03-16 13:29 ` Avi Kivity
2010-03-16 13:49 ` Yoshiaki Tamura
2010-03-16 13:51 ` Anthony Liguori
2010-03-16 13:57 ` Avi Kivity
2010-03-16 14:50 ` Anthony Liguori
2010-03-16 20:10 ` [Qemu-devel] " Blue Swirl
2010-03-16 22:31 ` Richard Henderson
2010-03-17 0:05 ` Paul Brook [this message]
2010-03-17 4:07 ` [Qemu-devel] " Avi Kivity
2010-03-17 16:06 ` Paul Brook
2010-03-17 16:28 ` Avi Kivity
2010-03-16 13:35 ` Anthony Liguori
2010-03-16 22:50 ` Yoshiaki Tamura
2010-03-16 10:53 ` [PATCH 3/6] qemu-kvm: Replace direct phys_ram_dirty access with wrapper functions Yoshiaki Tamura
2010-03-16 10:53 ` [PATCH 4/6] qemu-kvm: Introduce cpu_physical_memory_get_dirty_range() Yoshiaki Tamura
2010-03-16 12:47 ` Avi Kivity
2010-03-16 10:53 ` [PATCH 5/6] qemu-kvm: Use cpu_physical_memory_set_dirty_range() to update phys_ram_dirty Yoshiaki Tamura
2010-03-16 10:53 ` [PATCH 6/6] qemu-kvm: Use cpu_physical_memory_get_dirty_range() to check multiple dirty pages Yoshiaki Tamura
2010-03-16 13:11 ` [PATCH 0/6] qemu-kvm: Introduce bit-based phys_ram_dirty, and bit-based dirty page checker Avi Kivity
2010-03-16 13:41 ` Yoshiaki Tamura
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=201003170005.03822.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=ohmura.kei@lab.ntt.co.jp \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=tamura.yoshiaki@lab.ntt.co.jp \
/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