From: Geoffrey McRae <geoff@hostfission.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: hdanton@sina.com, tj@kernel.org, jiangshanlai@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: Poor windows VFIO performance, GPU stalls (bisected)
Date: Sun, 26 Jul 2020 23:32:13 +1000 [thread overview]
Message-ID: <a74373a54faf78541d96c28a00ae6757@hostfission.com> (raw)
In-Reply-To: <20200726073052.284dadb2@x1.home>
On 2020-07-26 23:30, Alex Williamson wrote:
> On Sun, 26 Jul 2020 17:49:07 +1000
> Geoffrey McRae <geoff@hostfission.com> wrote:
>
>> Hi All,
>>
>> The commit 22540ca3d00d2990a4148a13b92209c3dc5422db causes a Windows
>> KVM
>> guest running under QEMU with a VFIO passthrough GPU to randomly stall
>> when using the GPU leading to the guest assuming that the driver has
>> hung. Reverting this commit resolves the problem.
>
> Please double check this commit ID, I can't find it in mainline or
> linux-next. Thanks,
>
> Alex
Confirmed:
https://github.com/torvalds/linux/commit/22540ca3d00d2990a4148a13b92209c3dc5422db
>
>> The host system is configured with the following kernel arguments
>> which
>> may be related:
>> isolcpus=0-5,24-29,6-11,30-35 rcu_nocbs=0-5,24-29,6-11,30-35
>>
>> The system is an AMD Threadripper 2970WX on a Gigabyte x399 AORUS
>> Gaming
>> 7 board.
>> It has two GPUs each being passed through to two separate KVM guests,
>> one is an AMD Radeon 7 in a Linux guest, the other is a GeForce 1080Ti
>> in a Windows guest.
>> The cores used for these two guests are isolated from the host for
>> performance reasons.
>>
>> Any insight as to why this is occurring would be appreciated. If you
>> need any more information or would like to test patches please let me
>> know.
>>
>> Kind Regards,
>> Geoffrey McRae
>> HostFission
>>
>> https://hostfission.com
>>
next prev parent reply other threads:[~2020-07-26 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 7:49 Geoffrey McRae
2020-07-26 13:30 ` Alex Williamson
2020-07-26 13:32 ` Geoffrey McRae [this message]
2020-07-26 13:33 ` Geoffrey McRae
2020-07-26 14:15 ` Chris Wilson
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=a74373a54faf78541d96c28a00ae6757@hostfission.com \
--to=geoff@hostfission.com \
--cc=alex.williamson@redhat.com \
--cc=hdanton@sina.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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
all inboxes | Powered by JetHome®