From: Stefan Hajnoczi <stefanha@gmail.com>
To: iscccc <hellokittyme@163.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] cpu_memory_rw_debug function is too slow
Date: Wed, 4 Apr 2018 10:47:12 +0100 [thread overview]
Message-ID: <20180404094712.GJ4467@stefanha-x1.localdomain> (raw)
In-Reply-To: <69678ef4.64d2.1626aefe0be.Coremail.hellokittyme@163.com>
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
On Wed, Mar 28, 2018 at 12:48:48PM +0800, iscccc wrote:
> Hello, I found that use cpu_memory_rw_debug in tcg mode when qemu access guest virtual address is too slow, can I choose to use some other more fast function ?
Please explain what you are trying to do. It's hard for anyone to give
advice without context.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-04-04 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 4:48 [Qemu-devel] cpu_memory_rw_debug function is too slow iscccc
2018-04-04 9:47 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-28 4:52 张王俊杰
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=20180404094712.GJ4467@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=hellokittyme@163.com \
--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 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).