Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Nick H <nickkvm@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: __direct_map() questions
Date: Wed, 11 Jan 2012 17:13:33 -0200	[thread overview]
Message-ID: <20120111191333.GB13298@amt.cnet> (raw)
In-Reply-To: <CAMou0=wJiYssMQSv_Ct3J9TsNPRQ0icr4u+zV4OpyNsRvvKFWg@mail.gmail.com>

Hi,

See Documentation/virtual/kvm/mmu.txt in the kernel source tree.

On Tue, Jan 10, 2012 at 11:41:41AM -0800, Nick H wrote:
> Hello All,
> 
> I am preparing for a presentation for my community college, newbie to
> the kvm world. I am trying to understand kvm implementation. I am
> interested in doing a small presentation  on kvm and its internals at
> my school. I am looking at __direct_map() . I see
> for_each_shadow_entry()->shadow_walk_xxx()  (called in context of
> handle_ept_violation() ) functions using the gfn to find the
> iterator.sptep. It passes this iterator.sptep to the mmu_set_spte().

  reply	other threads:[~2012-01-11 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 19:41 __direct_map() questions Nick H
2012-01-11 19:13 ` Marcelo Tosatti [this message]
2012-01-15  1:36   ` Nick H

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=20120111191333.GB13298@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=nickkvm@gmail.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