All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: Mapping of Shared Page in e500 Powerpc kvm
Date: Tue, 25 Oct 2011 20:38:58 +0000	[thread overview]
Message-ID: <4EA71E62.2090302@freescale.com> (raw)
In-Reply-To: <loom.20111023T153549-514@post.gmane.org>

On 10/23/2011 08:45 AM, Aashish Mittal wrote:
> Hi
> 
> I'm working on powerpc e500 machine (Freescale P2020RDB machine) and 
> using the paravirtualization guest support available inside kvm  and wanted
>  to some bookkeeping of my own on the shared page and from what i 
> understood is that a single tlb entry is reserved for the shared page 
> (magic page) when running the guest which is never preempted or flushed
>  but when i tried printing out the dtlb misses on this shared page it show 
> me a large number of dtlb misses on this shared page which means that 
> this page is being preempted or flushed out in some way . Can someone pleas
> e clarify this situation if i'm understanding something wrong or is it a bug ?

What kernel are you running, and how many is "a large number"?

The magic page TLB entry will need to be reloaded if the shadow PID gets
invalidated, another guest gets scheduled on that CPU, or if something
like hugetlbfs steps on that TLB entry.

If you're running a kernel that predates shadow PID support, it will be
invalidated (along with everything else in the TLB) whenever you
schedule out or change guest execution mode .

-Scott


      parent reply	other threads:[~2011-10-25 20:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-23 13:45 Mapping of Shared Page in e500 Powerpc kvm Aashish Mittal
2011-10-23 15:14 ` Alexander Graf
2011-10-25 20:38 ` Scott Wood [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=4EA71E62.2090302@freescale.com \
    --to=scottwood@freescale.com \
    --cc=kvm-ppc@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 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.