[Xen-devel] stale TLB contents?

To:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] stale TLB contents?
From:	Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date:	Mon, 24 Jan 2011 14:00:58 +0100
Delivery-date:	Mon, 24 Jan 2011 05:02:11 -0800
Dkim-signature:	v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=juergen.gross@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1295874062; x=1327410062; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; z=Message-ID:=20<4D3D780A.4030001@xxxxxxxxxxxxxx>\|Date:=20 Mon,=2024=20Jan=202011=2014:00:58=20+0100\|From:=20Juergen =20Gross=20<juergen.gross@xxxxxxxxxxxxxx>\|MIME-Version: =201.0\|To:=20"xen-devel@xxxxxxxxxxxxxxxxxxx"=20<xen-devel @lists.xensource.com>\|Subject:=20stale=20TLB=20contents? \|Content-Transfer-Encoding:=207bit; bh=CIKooyljJoE7FF72YMyITOeufibxwOKU1ngK5CReKig=; b=uZQopU2gDlId0j59qoezJLUWqWkfRyDJaZ74B45XpZnEgHl5m3MGIISv 7yc6N5zHCNcZxSyiOQ4N2n9nzADHY8LEr4MSRE4OtZ8MakBIzj8G1Gci0 3qDdy6bdyG5HB5XLXOS9vESl3KiSbBguP0iPFwZP3wxMFBEVR5lkfuym1 3PQavsP1hoPq76jdoqXnR0Vx97u9Vq4bv40SmLZ2x+lpH3uIm9aumgGRu 3oMW9tSTtAceJIul6JnhNRbiKrkvl;
Domainkey-signature:	s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=jcAMJMeK9YvrMu/ieueszTtUuYtsKNRHXQ7qpCYAywYz+vy6Hrs8l1P+ 5br4AC3ynqe4in/gLdHly7XrYQOD28HlC9nV+ktK/1V0VTtRtAp69Q5SF SQnt0PNQA3qaFmTaK7ptsH4gwGgrSvY1xb2LBJEf/6yOAtQCna3TpKt6c P3CoavPQZ77QvJLrv5UyX59l6tFyFzqgP19IXON1HBJQnOem9ezG3QWhS ERpKzndVJiI1Frm0ti6zV6dSELwKY;
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization:	Fujitsu Technology Solutions
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101226 Iceowl/1.0b1 Icedove/3.0.11

Hi,

in our BS2000 guest running as HVM with EPT on x86_64 I have a problem which
seems to be related to stale TLB entries. I'm pretty sure I have invalidated
the TLB correctly after a change of the page tables, so I've searched for
possible problems in the hypervisor.

Xen is version 4.0 from SLES 11 SP1.

If I have read the sources correctly, neither INVLPG nor reload of CR3 are
handled by the hypervisor. And I didn't find an explicit clearing of the TLB
when a vcpu is switching physical cpus. So I think the following scenario is
possible:

- a vcpu is running on physical cpu A creating a TLB entry
- the vcpu is scheduled on physical cpu B, while physical cpu A is left idle
- on physical cpu B the TLB entry is cleared by INVLPG or load CR3
- the vcpu is scheduled on physical cpu A again (no other vcpu was active
  there in between), CR3 is same as when vcpu left cpu A
- the old TLB entry from the vcpu is still valid there!

Do I miss something?


Juergen

--
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] stale TLB contents?