From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 81841] amd-iommu: kernel BUG & lockup after shutting down KVM
 guest using PCI passthrough/PCIe bridge
Date: Tue, 12 Aug 2014 10:30:30 +0000
Message-ID: <bug-81841-28872-ROcN4XOAyN@https.bugzilla.kernel.org/>
References: <bug-81841-28872@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.kernel.org ([198.145.19.201]:36993 "EHLO mail.kernel.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751220AbaHLKae (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 12 Aug 2014 06:30:34 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
	by mail.kernel.org (Postfix) with ESMTP id 241A4200E8
	for <kvm@vger.kernel.org>; Tue, 12 Aug 2014 10:30:33 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org [172.20.200.51])
	by mail.kernel.org (Postfix) with ESMTP id 9700A200ED
	for <kvm@vger.kernel.org>; Tue, 12 Aug 2014 10:30:30 +0000 (UTC)
In-Reply-To: <bug-81841-28872@https.bugzilla.kernel.org/>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

https://bugzilla.kernel.org/show_bug.cgi?id=81841

--- Comment #13 from Marti Raudsepp <marti@juffo.org> ---
(In reply to Joerg Roedel from comment #12)
> Thanks, Joerg

Indeed. Thanks, Joerg. And thanks everyone else too, you have been very
helpful!

I didn't have v3.13 sources handy, but I applied the attachment 146311 patch to
3.16.0 and it fixes the problem. (I verified that unpatched 3.16.0 also
crashes).

I can start & shut down the VM multiple times without crashing the host and PCI
passthrough works as expected.

Feel free to add
    Tested-by: Marti Raudsepp <marti@juffo.org>

(In reply to Alex Williamson from comment #7)
> Note that it's not required to assign all the devices, they simply need to
> be detached from host drivers (ie. bound to pci-stub or vfio-pci).

This approach also works; I think I will go this route for the production
setup. Seems that we don't actually need any of the devices in the same IOMMU
group.

(In reply to Joel Schopp from comment #10)
> > AMD would need to confirm it.
>
> I don't have an answer for you offhand.  Let me do some digging and get you
> an answer.

I am sorry if I sounded frustrated or arrogant earlier. Any update on this?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.