From nobody Thu Oct 31 23:48:28 2024 Delivered-To: importer@patchew.org Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1674809241; cv=none; d=zohomail.com; s=zohoarc; b=Jl+tyslFjO3SqeXlyjhTilCveHEy/wVZuQbYdY25fwiyO3KdEPG66qXz4VtOoTwrDK4X1t04PF28225viI/DySm2F8ND6V02O6C/uXK40mifL0wNG9CoIgxSlOND8O/G7n8NeaGX0Rapstgyu1n0u+yxeNSzCE7iSRJl3905hxg= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1674809241; h=Content-Transfer-Encoding:Cc:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To; bh=QowdSqtOHVhy09/uvKCJooHqAkCnUDBA/EgzQksY1UI=; b=aqmuuovfQr66MIBjvop1UC1eQZTcFr3sy5ubcWIpEATZ8+k13aRhwdRFnL3pyGdyhCWV4CILNM7F0WB4MBpqaJCUCcVo1R5Aewf90pYzU88SWlAmUBkEDZLNUuqLCwVC33PA8h5ukJHYKdSyS+Ms0iNLZnH0CqDOvgYCvTMXauo= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) by mx.zohomail.com with SMTPS id 1674809241780945.0848869616874; Fri, 27 Jan 2023 00:47:21 -0800 (PST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pLKNE-0000hO-3C; Fri, 27 Jan 2023 03:46:16 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pLKNC-0000gz-Ct for qemu-devel@nongnu.org; Fri, 27 Jan 2023 03:46:14 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pLKNA-0000g4-Ny for qemu-devel@nongnu.org; Fri, 27 Jan 2023 03:46:14 -0500 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-668-_lF5rw43OKKKpnBbr7d_tQ-1; Fri, 27 Jan 2023 03:46:07 -0500 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C455E802C18; Fri, 27 Jan 2023 08:46:06 +0000 (UTC) Received: from fedora.. (ovpn-194-166.brq.redhat.com [10.40.194.166]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3C3D32026D4B; Fri, 27 Jan 2023 08:46:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1674809172; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=QowdSqtOHVhy09/uvKCJooHqAkCnUDBA/EgzQksY1UI=; b=AlLYB8uuJciJ1Bn6VvOtsYLb7MFLjEhB6RVxGl5qDJwE8bELKPIpiA8mZjS/cBoCXgfuBy vGXy3KAtm1ks9I3t7W2j/+RZfP8+qFiXNTCpyNClQ1clwvQtbU9liUWgfOZJBSyfKK3MaD htM5Zz1FV4xNjkyWMTNrMiBNx+U7qkc= X-MC-Unique: _lF5rw43OKKKpnBbr7d_tQ-1 From: Sebastian Mitterle To: qemu-devel@nongnu.org Cc: thuth@redhat.com, cohuck@redhat.com, clegoate@redhat.com, qemu-trivial@nongnu.org, qemu-s390x@nongnu.org Subject: [PATCH v2] docs/s390x/pcidevices: document pci devices on s390x Date: Fri, 27 Jan 2023 09:46:04 +0100 Message-Id: <20230127084604.53175-1-smitterl@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 Received-SPF: pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) client-ip=209.51.188.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Received-SPF: pass client-ip=170.10.133.124; envelope-from=smitterl@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: qemu-devel-bounces+importer=patchew.org@nongnu.org X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1674809243365100002 Content-Type: text/plain; charset="utf-8" Add some documentation about the zpci device and how to use it with pci devices on s390x. Used source: Cornelia Huck's blog post https://people.redhat.com/~cohuck/2018/02/19/notes-on-pci-on-s390x.html Signed-off-by: Sebastian Mitterle Reviewed-by: C=C3=A9dric Le Goater --- v2: move section below 'Device support' --- docs/system/s390x/pcidevices.rst | 34 ++++++++++++++++++++++++++++++++ docs/system/target-s390x.rst | 1 + 2 files changed, 35 insertions(+) create mode 100644 docs/system/s390x/pcidevices.rst diff --git a/docs/system/s390x/pcidevices.rst b/docs/system/s390x/pcidevice= s.rst new file mode 100644 index 0000000000..fec905d6e6 --- /dev/null +++ b/docs/system/s390x/pcidevices.rst @@ -0,0 +1,34 @@ +PCI devices on s390x +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + +PCI devices on s390x work differently than on other architectures. + +To start with, using a PCI device requires the additional ``zpci`` device.= For example, +in order to pass a PCI device ``0000:00:00.0`` through you'd specify:: + + qemu-system-s390x ... \ + -device zpci,uid=3D1,fid=3D0,target=3Dhostdev0,id=3Dzpc= i1 \ + -device vfio-pci,host=3D0000:00:00.0,id=3Dhostdev0 + +Here, the zpci device is joined with the PCI device via the ``target`` pro= perty. + +Note that we don't set bus, slot or function here for the guest as is comm= on in other +PCI implementations. Topology information is not available on s390x. Inste= ad, ``uid`` +and ``fid`` determine how the device is presented to the guest operating s= ystem. + +In case of Linux, ``uid`` will be used in the ``domain`` part of the PCI i= dentifier, and +``fid`` identifies the physical slot, i.e.:: + + qemu-system-s390x ... \ + -device zpci,uid=3D7,fid=3D8,target=3Dhostdev0,id=3Dzpc= i1 \ + ... + +will be presented in the guest as:: + + # lspci -v + 0007:00:00.0 ... + Physical Slot: 00000008 + ... + +Finally, note that you might have to enable the ``zpci`` feature in the cp= u model in oder to use +it. diff --git a/docs/system/target-s390x.rst b/docs/system/target-s390x.rst index c636f64113..f6f11433c7 100644 --- a/docs/system/target-s390x.rst +++ b/docs/system/target-s390x.rst @@ -26,6 +26,7 @@ or vfio-ap is also available. s390x/css s390x/3270 s390x/vfio-ccw + s390x/pcidevices =20 Architectural features =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --=20 2.37.3