From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2B0D8C761AF for ; Sat, 1 Apr 2023 14:44:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230140AbjDAOon (ORCPT ); Sat, 1 Apr 2023 10:44:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57916 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230158AbjDAOol (ORCPT ); Sat, 1 Apr 2023 10:44:41 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5555B1D862; Sat, 1 Apr 2023 07:44:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1680360280; x=1711896280; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=y2zlxKZ9NOOslsssQl+DjQN7OV6B46QdrinsLbD5orE=; b=CCOMdBGrP7PsKfATceXEu+I6dCP66P8OzWohzY34P1Rec3u8FyjgViVq Iu5/rrL1ZyanJBIB0hzBh4L9DONJShGo8vDhmvbtFa/qNkJZVR7FEUOKj EvjBn2KLgqoD4zIweWVIE+LcIkkox0qdcA5k+ZClShhEI8WCGfp2bGhkI HbjX7s0KXDaJ8iYzTQZ1D/OJubhnRzVKeqV8OUJIld1bwkII41qjF1hKI yqz8qeXkXbm+4elanZJcj8XaPG/7ees+RdHiL5GvccoBpEsv+sfhBwLXv 1DwBJPhu6c+u5lTLyQ4xu2JWtbgfN0lVMNgVaKIZzySrbymzv+dluBCEe g==; X-IronPort-AV: E=McAfee;i="6600,9927,10667"; a="340385173" X-IronPort-AV: E=Sophos;i="5.98,310,1673942400"; d="scan'208";a="340385173" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Apr 2023 07:44:40 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10667"; a="662705859" X-IronPort-AV: E=Sophos;i="5.98,310,1673942400"; d="scan'208";a="662705859" Received: from 984fee00a4c6.jf.intel.com ([10.165.58.231]) by orsmga006.jf.intel.com with ESMTP; 01 Apr 2023 07:44:39 -0700 From: Yi Liu To: alex.williamson@redhat.com, jgg@nvidia.com, kevin.tian@intel.com Cc: joro@8bytes.org, robin.murphy@arm.com, cohuck@redhat.com, eric.auger@redhat.com, nicolinc@nvidia.com, kvm@vger.kernel.org, mjrosato@linux.ibm.com, chao.p.peng@linux.intel.com, yi.l.liu@intel.com, yi.y.sun@linux.intel.com, peterx@redhat.com, jasowang@redhat.com, shameerali.kolothum.thodi@huawei.com, lulu@redhat.com, suravee.suthikulpanit@amd.com, intel-gvt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, linux-s390@vger.kernel.org, xudong.hao@intel.com, yan.y.zhao@intel.com, terrence.xu@intel.com, yanting.jiang@intel.com Subject: [PATCH v3 11/12] iommufd: Define IOMMUFD_INVALID_ID in uapi Date: Sat, 1 Apr 2023 07:44:28 -0700 Message-Id: <20230401144429.88673-12-yi.l.liu@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230401144429.88673-1-yi.l.liu@intel.com> References: <20230401144429.88673-1-yi.l.liu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-s390@vger.kernel.org as there are IOMMUFD users that want to know check if an ID generated by IOMMUFD is valid or not. e.g. vfio-pci optionaly returns invalid dev_id to user in the VFIO_DEVICE_GET_PCI_HOT_RESET_INFO ioctl. User needs to check if the ID is valid or not. IOMMUFD_INVALID_ID is defined as 0 since the IDs generated by IOMMUFD starts from 0. Signed-off-by: Yi Liu --- include/uapi/linux/iommufd.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/include/uapi/linux/iommufd.h b/include/uapi/linux/iommufd.h index 98ebba80cfa1..aeae73a93833 100644 --- a/include/uapi/linux/iommufd.h +++ b/include/uapi/linux/iommufd.h @@ -9,6 +9,9 @@ #define IOMMUFD_TYPE (';') +/* IDs allocated by IOMMUFD starts from 0 */ +#define IOMMUFD_INVALID_ID 0 + /** * DOC: General ioctl format * -- 2.34.1