From: Avi Kivity <avi@redhat.com>
To: cs-jerry** <jerry.wzy@qq.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: confusion about kvm_mmu_pte_write
Date: Tue, 24 Aug 2010 12:54:21 +0300 [thread overview]
Message-ID: <4C7396CD.4020506@redhat.com> (raw)
In-Reply-To: <tencent_0C07948E3D9695BC5198FE45@qq.com>
On 08/24/2010 11:16 AM, cs-jerry** wrote:
> hello all,
> i am reading kvm code and confused about the mmu_pte_write process,
> when update a gpte, function kvm_mmu_pte_write is called , and walk the shadow page for it.why condition is :
> if (sp->gfn != gfn || sp->role.direct || sp->role.invalid)
> continue;
> and not update those sp->gfn == gfn&& sp->role.direct,what does it mean when role.direct is clear?
> thanks.N‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·¤¾h§¶\x17›¡Ü¨}©ž²Æ zÚ&j:+v‰¨¾\a«‘êçzZ+€Ê+zf£¢·hšˆ§~††Ûiÿûàz¹\x1e®w¥¢¸?™¨èÚ&¢)ߢ^[fl===
Please fix you mail client not to send corrupted emails. Also, read
Documentation/kvm/mmu.txt.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-08-24 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 8:16 confusion about kvm_mmu_pte_write cs-jerry**
2010-08-24 9:54 ` Avi Kivity [this message]
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=4C7396CD.4020506@redhat.com \
--to=avi@redhat.com \
--cc=jerry.wzy@qq.com \
--cc=kvm@vger.kernel.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