public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: "Liu Yu" <Yu.Liu@freescale.com>
Cc: "Hollis Blanchard" <hollisb@us.ibm.com>,
	avi@qumranet.com, kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 5 of 5] kvm: powerpc: Map guest userspace with TID=0 mappings
Date: Tue, 29 Jul 2008 09:03:08 +0200	[thread overview]
Message-ID: <200807290903.08763.ehrhardt@linux.vnet.ibm.com> (raw)
In-Reply-To: <E20ABADA5792574791053954EC20B59509B402@zch01exm26.fsl.freescale.net>

On Monday 28 July 2008 12:33:41 Liu Yu wrote:
> I have a question that I could not think through.
> While multiple qemu/kvm processes are running at the same time, how to
> prevent one guest from using others' TLB? For all the guests have the
> same TID=0 for userspace and TID=1 for kernel.
[...]

Hi Yu Liu, thats a good question.
Afaik thats solved by the fact that the shadow tlb which is used when entering 
guest context is per vcpu. Therefor a guest has always it's own shadow tlb 
active and no mappings to the content of other guests.

This patch just allows us that a single guest userspace process accessing the 
kernel 20 times (and changing privilege level 20 times by doing so) can run 
without tlb flushes.
Guest-userspace context switch (pid is changing) -> tlb flush; and guest 
switches (guest A -> guest B) -> other shadow tlb active; should still be 
working fine.

> >
> > The net is that we don't need to flush the TLB on privilege
> > switches, but we do on guest context switches (which are far
> > more infrequent). Guest boot time performance improvement: about 30%.
> >

-- 

Grüsse / regards, 
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization

  reply	other threads:[~2008-07-29  7:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 18:54 [PATCH 0 of 5] PowerPC patches for 2.6.27 Hollis Blanchard
     [not found] ` <patchbomb.1217012088-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-07-25 18:54   ` [PATCH 1 of 5] kvm: ppc: guest breakpoint support Hollis Blanchard
2008-07-25 18:54   ` [PATCH 2 of 5] kvm: ppc: fix invalidation of large guest pages Hollis Blanchard
2008-07-25 18:54   ` [PATCH 3 of 5] kvm: ppc: Stop saving host TLB state Hollis Blanchard
2008-07-25 18:54   ` [PATCH 4 of 5] kvm: ppc: Write only modified shadow entries into the TLB on exit Hollis Blanchard
2008-07-25 18:54   ` [PATCH 5 of 5] kvm: powerpc: Map guest userspace with TID=0 mappings Hollis Blanchard
     [not found]     ` <080b9c9515a5593babc8.1217012093-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-07-28 10:33       ` Liu Yu
2008-07-29  7:03         ` Christian Ehrhardt [this message]
2008-07-29  7:48           ` Liu Yu
2008-07-29 10:56             ` Liu Yu
2008-07-27  8:50   ` [PATCH 0 of 5] PowerPC patches for 2.6.27 Avi Kivity
     [not found]     ` <488C36DE.70507-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-07-29  7:20       ` Christian Ehrhardt
2008-07-29 13:00         ` Avi Kivity

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=200807290903.08763.ehrhardt@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=Yu.Liu@freescale.com \
    --cc=avi@qumranet.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --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