All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Marek Olszewski <mareko@csail.mit.edu>
Cc: kvm@vger.kernel.org
Subject: Re: KVM Page Fault Question
Date: Fri, 02 Apr 2010 09:39:19 +0300	[thread overview]
Message-ID: <4BB59117.2040903@redhat.com> (raw)
In-Reply-To: <4BB57596.6090109@csail.mit.edu>

On 04/02/2010 07:41 AM, Marek Olszewski wrote:
> When a guest OS writes to a shadowed (and therefore page protected) 
> guest page table, does the resulting page fault get handled in 
> paging_tmpl.h:xxx_page_fault or does it call some rmap related code 
> directly? 

page faults are dispatched to the page_fault callback.

> Also, what does the "direct" mmu page role mean?
>

It means that the page maps the linear range (gfn << 12)..(((gfn + (1 << 
level*9))) << 12) instead of shadowing a guest page table at gfn.  
Useful for real mode, large pages, and tdp.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2010-04-02  6:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  4:57 Shadow page table questions Marek Olszewski
2010-03-10  9:47 ` Avi Kivity
2010-03-11  0:06   ` Marek Olszewski
2010-03-11  6:39     ` Avi Kivity
2010-03-11 16:14       ` Marek Olszewski
2010-03-13  8:51         ` Avi Kivity
2010-03-18 23:50           ` KVM Page Fault Question Marek Olszewski
2010-03-19  8:39             ` Avi Kivity
2010-04-02  4:41               ` Marek Olszewski
2010-04-02  6:39                 ` Avi Kivity [this message]
     [not found]                   ` <4BB614BC.9080608@csail.mit.edu>
2010-04-04 16:59                     ` Avi Kivity
2010-04-22  5:26                       ` Marek Olszewski
2010-04-22  6:52                         ` Avi Kivity
     [not found]                           ` <4BD0DFBE.1090103@csail.mit.edu>
2010-04-26  5:42                             ` Marek Olszewski
2010-05-20  2:24                           ` Shadow MMU state preserved across kvm_mmu_zap_all? Marek Olszewski

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=4BB59117.2040903@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mareko@csail.mit.edu \
    /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.