public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Prasad Joshi <prasadjoshi124@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Page Eviction Algorithm
Date: Thu, 28 Oct 2010 10:44:28 +0200	[thread overview]
Message-ID: <4CC937EC.9010000@redhat.com> (raw)
In-Reply-To: <AANLkTi=GfK5RGq=XLZc-q=L9Q5tZQuq4ePy8BeYWp5Cu@mail.gmail.com>

  On 10/26/2010 03:31 PM, Prasad Joshi wrote:
> On Tue, Oct 26, 2010 at 2:07 PM, Avi Kivity<avi@redhat.com>  wrote:
> >    On 10/26/2010 12:42 PM, Prasad Joshi wrote:
> >>
> >>  Thanks a lot for your reply.
> >>
> >>  On Tue, Oct 26, 2010 at 11:31 AM, Avi Kivity<avi@redhat.com>    wrote:
> >>  >      On 10/26/2010 11:19 AM, Prasad Joshi wrote:
> >>  >>
> >>  >>    Hi All,
> >>  >>
> >>  >>    I was just going over TODO list on KVM page. In MMU related TODO I saw
> >>  >>    only page eviction algorithm currently implemented is FIFO.
> >>  >>
> >>  >>    Is it really the case?
> >>  >
> >>  >    Yes.
> >>  >
> >>  >>    If yes I would like to work on it. Can someone
> >>  >>    let me know the place where the FIFO code is implemented?
> >>  >
> >>  >    Look at the code that touches mmu_active_list.
> >>  >
> >>  >    FWIW improving the algorithm is not critically important.  It's rare
> >>  >  that
> >>  >    mmu shadow pages need to be evicted.
> >>
> >>  I would be doing a University project on Virtualization. I would like
> >>  to work on Linux kernel and KVM. I was looking over the TODO list on
> >>  KVM wiki.
> >>
> >>  Can you please suggest me something that would add value to KVM?
> >>
> >
> >  O(1) write protection (on the TODO page) is interesting and important.  It's
> >  difficult, so you may want to start with O(1) invalidation.
>
> I am not sure if I can understand what exactly is a MMU invalidation.
> Is it cache invalidation or TLB invalidation? Can you please
> elaborate. I am really sorry if I am asking a silly question.

Invalidation of all shadow page tables.  The current code which does 
this is in kvm_mmu_zap_all().

-- 
error compiling committee.c: too many arguments to function


      parent reply	other threads:[~2010-10-28  8:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  9:19 Page Eviction Algorithm Prasad Joshi
2010-10-26 10:31 ` Avi Kivity
2010-10-26 10:42   ` Prasad Joshi
2010-10-26 13:07     ` Avi Kivity
2010-10-26 13:31       ` Prasad Joshi
2010-10-26 15:08         ` Prasad Joshi
2010-10-28  8:45           ` Avi Kivity
2010-10-28 13:03             ` Prasad Joshi
2010-10-28  8:44         ` 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=4CC937EC.9010000@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=prasadjoshi124@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