[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Need help to debug Arm SMMU issue seen on guests with passthrough devices
 
- To: Rahul Singh <rahul.singh@xxxxxxx>, ", Bertrand Marquis"	<Bertrand.Marquis@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>,	Julien Grall <julien@xxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, ", Volodymyr Babchuk" <Volodymyr_Babchuk@xxxxxxxx>
 
- From: Ayan Kumar Halder <ayan.kumar.halder@xxxxxxxxxx>
 
- Date: Thu, 21 Apr 2022 12:12:14 +0100
 
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 149.199.80.198) smtp.rcpttodomain=arm.com smtp.mailfrom=xilinx.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=xilinx.com; dkim=none (message not signed); arc=none
 
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ayjYtlWkn1QhSNk4ar55+UT61YtxMb725DAP9tz1D/M=; b=lGQ++RfIUcJrgWYnKrjYNjLEkWz7IatiKwlNVDRUOb700m9tnN7OMef+ur5GPil8QLBuJY94Je5jouBMK59U2JqhX/SyxrTxsCXQwV3gziY6f3kREYdb8DAulxm55XgHo7pi0oczl2+LLZAK281SQ4FjQ041SeDEpJemeCqr0P6Tww0IvoDkzlsg9rwewt518v55g4KR1MS8S+POjlIum8tnEkF9IFkZ/PtoFxvArsoqEqwiLx0ceZ4GGIOX/Cw4cuAD8HUlgyWlBcDSJqvT4AGit6UCeMecSRACU9j0SUIS7aTqyjS4P8DUNvpN+YmuO7/hjCB3wyTmmpVbdyHPIQ==
 
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BpdknWLIhQ+uQuDGKtIoEprSMA0lEil3zC3eLjonucVVO2/AWreKejSgbvQEz+QPh4sFCv3VAX0/EU7RTDENn4FHgPjBrNYrpYECNAaoQUKuU3HKrD40mtEtjdx5tr7WoEVH4Yv6r6twAJhivIUSc+/fHnsL21X/XP61QKX3AzJROQXHfnUbKZNdT7lVf1NRkO2rsHSgf2rO7vi4KT+7fxPksTibHhnQiEc101INzxeBZYHjFYsmoam+QehjoKloqVvseMJLkJLeIkqLDMNBmHp5P/PkcDS16kK03YHTWSM/3rtgr22A2G9dm7Or229WTVr2UXvZ5CZTQ2D+1ZqiDA==
 
- Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
 
- Delivery-date: Thu, 21 Apr 2022 11:12:23 +0000
 
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
 
 
 
Hi Arm/SMMU experts,
 Scenario :- I am trying to assign a device (eg mmc) to a guest which 
uses smmu. I start the guest using "xl create -c ...". It works fine for 
the first time. I am able to access the device.
Now, when I destroy the guest and create again, I see this issue
 (XEN) smmu: /axi/smmu@fd800000:         GFSR 0x00000002, GFSYNR0 
0x00000000, GFSYNR1 0x00000871, GFSYNR2 0x00000000
0x871 is the stream id used by mmc.
 We are using SMMU-500. So from the Arm SMMU v2 specs, it is 
"Unidentified stream fault" for stream id "0x871".
 This issue is seen regardless we use 'mmu-masters' or 'iommus' property 
in xen device tree.
 I can confirm that this issue was not seen in xen-4.14.3. It is seen in 
our (Xilinx's) latest release ie xen-4.16.1.
 I am using our downstream fork of Xen. I can't readily use the upstream 
as we use lot of EEMI codebase.
Can someone try to see if this issue exists in the latest upstream Xen ?
Any pointers on how to debug this further ?
Kind regards,
Ayan
 
 
    
     |