From: Tomasz Wroblewski <tomasz.wroblewski@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: jinsong.liu@intel.com, JBeulich@suse.com
Subject: GPU passthrough performance regression in >4GB vms due to XSA-60 changes
Date: Thu, 15 May 2014 11:11:05 +0200 [thread overview]
Message-ID: <537484A9.9000001@gmail.com> (raw)
Hello,
We've recently updated from Xen 4.3.1 to 4.3.2 and found out a major
regression in gpu passthrough performance in VMs using >4GB of memory.
When using GPU pt (some radeon cards, also intergrated intel gpu pt),
load on cpu is constantly near maximum and screen is slow to update. The
machines are intel haswell/ivybridge laptops/desktops, the guests are
windows 7 64-bit HVMs.
I've bisected the failure to be due to XSA-60 changes, specifically:
commit e81d0ac25464825b3828cff5dc9e8285612992c4
Author: Liu Jinsong <jinsong.liu@intel.com>
Date: Mon Dec 9 14:26:03 2013 +0100
VMX: remove the problematic set_uc_mode logic
This commit seems to have removed a bit of logic which, when guest was
setting cache disable bit in CR0 for a brief time, was iterating on all
mapped pfns and resetting memory type in EPTs to be consistent with the
result of mtrr.c:epte_get_entry_emt() call. I believe my tracing
indicates this used to return WRITEBACK caching strategy for the 64bit
memory areas where the BARs of the gpu seem to be located.
This bit of code is not happening anymore, speculatively I think the PCI
BAR area stays as uncached which causes the general slowness. Note that
I'm not talking about slow performance during the window the CR0 has
caching disabled, it does stays slow even after guest reenables it
shortly after since the problem seems to be a side effect of removed
loop setting some default EPT policies on all pfns. Reintroducing the
removed loop fixes the problem.
Would welcome comments/ideas how to debug this more, or maybe there's an
obvious fix.
next reply other threads:[~2014-05-15 10:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 9:11 Tomasz Wroblewski [this message]
2014-05-15 12:32 ` GPU passthrough performance regression in >4GB vms due to XSA-60 changes Jan Beulich
2014-05-15 12:10 ` Tomasz Wroblewski
2014-05-15 13:23 ` Jan Beulich
2014-05-15 13:39 ` Tomasz Wroblewski
2014-05-15 14:34 ` Tomasz Wroblewski
2014-05-15 14:56 ` Tomasz Wroblewski
2014-05-15 16:07 ` Jan Beulich
2014-05-15 15:39 ` Tomasz Wroblewski
2014-05-16 6:33 ` Jan Beulich
2014-05-16 11:18 ` Tomasz Wroblewski
2014-05-16 11:38 ` Jan Beulich
2014-05-16 14:36 ` Jan Beulich
2014-05-19 10:29 ` Tomasz Wroblewski
2014-05-19 10:38 ` Jan Beulich
2014-05-19 10:47 ` Tomasz Wroblewski
2014-05-19 11:07 ` Jan Beulich
2014-05-19 11:32 ` Tomasz Wroblewski
2014-05-19 12:06 ` Jan Beulich
2014-05-19 12:17 ` Tomasz Wroblewski
2014-05-19 12:44 ` Jan Beulich
2014-05-19 14:20 ` Tomasz Wroblewski
2014-05-19 15:24 ` Jan Beulich
2014-05-19 15:48 ` Tomasz Wroblewski
2014-05-19 17:36 ` Tim Deegan
2014-05-20 6:31 ` Jan Beulich
2014-05-19 10:42 ` Tomasz Wroblewski
2014-05-19 11:01 ` Jan Beulich
2014-05-19 11:09 ` Tomasz Wroblewski
2014-05-19 11:19 ` Jan Beulich
2014-05-15 16:01 ` Jan Beulich
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=537484A9.9000001@gmail.com \
--to=tomasz.wroblewski@gmail.com \
--cc=JBeulich@suse.com \
--cc=jinsong.liu@intel.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).