From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 22A8D15CAF for ; Tue, 8 Nov 2022 14:05:02 +0000 (UTC) Received: from pps.filterd (m0187473.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 2A8DuQas018816; Tue, 8 Nov 2022 14:04:52 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=message-id : date : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding : mime-version; s=pp1; bh=Da4/O2Zd6WUKG4kUkKSzfI/XXsILh4u6FrSK9vP8CR4=; b=L94SbMbWrcR9dGMrLD0fzem+7JKCh2CTXoYi/1nJlevehDrfmTLUbo5JhR3LyDtIVfyN DI/hP/+sQtt0slqoi0GK1Ebs/S6HmPnIHXKYrSu2dSSiryfacnPxjyHqy40EzbbP3cO6 2cRPLQFnFl+LgfeblEWukK0NL2scue4A3QPHCopEArgRPrls/pnbseWNiJE/OQ93IgvX gqXkP4A03dp6GeB7xMdaONhfSK//gOUKBqyT8CFJGGcfrws5Zp2gjVyWrlspJ8AHZEeh XdIQOFS0IdMz4cbUJrhxi1rBvVTMbSa3unh0WFnU0DTcQ9+EKJRMGZBJ0xLNXKdVw5Y1 jQ== Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3kqkd8jdnd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 08 Nov 2022 14:04:52 +0000 Received: from m0187473.ppops.net (m0187473.ppops.net [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 2A8Cm7Oc013724; Tue, 8 Nov 2022 14:04:51 GMT Received: from ppma01wdc.us.ibm.com (fd.55.37a9.ip4.static.sl-reverse.com [169.55.85.253]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3kqkd8jdm3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 08 Nov 2022 14:04:51 +0000 Received: from pps.filterd (ppma01wdc.us.ibm.com [127.0.0.1]) by ppma01wdc.us.ibm.com (8.16.1.2/8.16.1.2) with SMTP id 2A8E4UX0009048; Tue, 8 Nov 2022 14:04:49 GMT Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by ppma01wdc.us.ibm.com with ESMTP id 3kngs3xxab-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 08 Nov 2022 14:04:49 +0000 Received: from smtpav06.dal12v.mail.ibm.com ([9.208.128.130]) by b03cxnp08025.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 2A8E4kVl29819370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 8 Nov 2022 14:04:46 GMT Received: from smtpav06.dal12v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2039C58061; Tue, 8 Nov 2022 14:04:48 +0000 (GMT) Received: from smtpav06.dal12v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0BEA358059; Tue, 8 Nov 2022 14:04:47 +0000 (GMT) Received: from [9.160.53.158] (unknown [9.160.53.158]) by smtpav06.dal12v.mail.ibm.com (Postfix) with ESMTP; Tue, 8 Nov 2022 14:04:46 +0000 (GMT) Message-ID: Date: Tue, 8 Nov 2022 09:04:46 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 Subject: Re: S390 testing for IOMMUFD Content-Language: en-US To: Christian Borntraeger , Jason Gunthorpe , Cornelia Huck , Eric Farman , Matthew Rosato , Niklas Schnelle , Halil Pasic , Jason Herne , linux-s390@vger.kernel.org Cc: iommu@lists.linux.dev, Kevin Tian , Alex Williamson , kvm@vger.kernel.org, Lu Baolu , Nicolin Chen References: <0-v4-0de2f6c78ed0+9d1-iommufd_jgg@nvidia.com> From: Anthony Krowiak In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed X-TM-AS-GCONF: 00 X-Proofpoint-ORIG-GUID: QCSdPSDvXQEZ3KcRAL7rMnNrY2zU-c9u X-Proofpoint-GUID: oDDYXrcvd-c8HddLK2SRDvjYSPtRFn4y Content-Transfer-Encoding: 8bit X-Proofpoint-UnRewURL: 0 URL was un-rewritten Precedence: bulk X-Mailing-List: iommu@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.895,Hydra:6.0.545,FMLib:17.11.122.1 definitions=2022-11-07_11,2022-11-08_01,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 lowpriorityscore=0 priorityscore=1501 mlxlogscore=999 mlxscore=0 phishscore=0 malwarescore=0 spamscore=0 suspectscore=0 impostorscore=0 clxscore=1011 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2210170000 definitions=main-2211080084 On 11/8/22 5:12 AM, Christian Borntraeger wrote: > > > Am 08.11.22 um 02:09 schrieb Jason Gunthorpe: >> On Mon, Nov 07, 2022 at 08:48:53PM -0400, Jason Gunthorpe wrote: >>> [ >>> This has been in linux-next for a little while now, and we've completed >>> the syzkaller run. 1300 hours of CPU time have been invested since the >>> last report with no improvement in coverage or new detections. >>> syzkaller >>> coverage reached 69%(75%), and review of the misses show substantial >>> amounts are WARN_ON's and other debugging which are not expected to be >>> covered. >>> ] >>> >>> iommufd is the user API to control the IOMMU subsystem as it relates to >>> managing IO page tables that point at user space memory. >> >> [chop cc list] >> >> s390 mdev maintainers, >> >> Can I ask your help to test this with the two S390 mdev drivers? Now >> that gvt is passing and we've covered alot of the QA ground it is a >> good time to run it. >> >> Take the branch from here: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git/log/?h=for-next >> > >> >> And build the kernel with >> >> CONFIG_VFIO_CONTAINER=n >> CONFIG_IOMMUFD=y >> CONFIG_IOMMUFD_VFIO_CONTAINER=y >> >> And your existing stuff should work with iommufd providing the iommu >> support to vfio. There will be a dmesg confirming this. > > Gave it a quick spin with vfio_ap: > [  401.679199] vfio_ap_mdev b01a7c33-9696-48b2-9a98-050e8e17c69a: > Adding to iommu group 1 > [  402.085386] iommufd: IOMMUFD is providing /dev/vfio/vfio, not VFIO. > > Some tests seem to work, but others dont (running into timeouts). I > need to look > into that (or ideally Tony will have a look, FWIW > tests.test_vfio_ap.VfioAPAssignMdevToGuestTest > fails for me. I'm looking into it. > > > The same kernel tree with defconfig (instead of > CONFIG_IOMMUFD_VFIO_CONTAINER=y) works fine. >> >> Let me know if there are any problems! >> >> If I recall there was some desire from the S390 platform team to start >> building on iommufd to create some vIOMMU acceleration for S390 >> guests, this is a necessary first step. >> >> Thanks, >> Jason