Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 17 Oct 2022 20:54:53 -0300
From:   Jason Gunthorpe <jgg@nvidia.com>
To:     Nicolin Chen <nicolinc@nvidia.com>, joro@8bytes.org
Cc:     will@kernel.org, robin.murphy@arm.com, kevin.tian@intel.com,
        quic_jjohnson@quicinc.com, suravee.suthikulpanit@amd.com,
        robdclark@gmail.com, dwmw2@infradead.org, baolu.lu@linux.intel.com,
        yong.wu@mediatek.com, matthias.bgg@gmail.com, orsonzhai@gmail.com,
        baolin.wang@linux.alibaba.com, zhang.lyra@gmail.com,
        thierry.reding@gmail.com, vdumpa@nvidia.com, jonathanh@nvidia.com,
        jean-philippe@linaro.org, tglx@linutronix.de,
        shameerali.kolothum.thodi@huawei.com,
        christophe.jaillet@wanadoo.fr, yangyicong@hisilicon.com,
        yangyingliang@huawei.com, quic_saipraka@quicinc.com,
        jon@solid-run.com, iommu@lists.linux.dev,
        linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-arm-msm@vger.kernel.org, linux-mediatek@lists.infradead.org,
        linux-tegra@vger.kernel.org,
        virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v7 0/5] Define EINVAL as device/domain incompatibility
Message-ID: <Y03rTb542P37J+EN@nvidia.com>
References: <cover.1666042872.git.nicolinc@nvidia.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cover.1666042872.git.nicolinc@nvidia.com>
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?BIM8VC1eKhRRCxwqoeoRVPgruN1CjsrDOXQ/YntJRCJUNQXxHlRHAwdmcc54?=
 =?us-ascii?Q?XCJhMF6gfUXaziQrXg/QZ9br3f9dwS2wRdnq27crqMMsp6KA/dzold/O90e8?=
 =?us-ascii?Q?masUAZW9LvDMz9BjfWODv/e5U4t9rzq4XV6X97w/0kx62fU5jPm9MmY+b43y?=
 =?us-ascii?Q?BdI8jaj7fF+iK7MgKaBWj2mONafpFpCNMw8rR8HOEdD3gtuESBkqolLrk0u3?=
 =?us-ascii?Q?B2gyM7hgknjvcZPtSY4+TVMWtWE6OiWit0aC9wxbP2PKuvk5Y0dASpZNqp+n?=
 =?us-ascii?Q?99AoRsbiQ0Wh69NIrjI1u39tV/4mOpzDNy6JzVTDWyNNAfnYpDlSMqZehwrT?=
 =?us-ascii?Q?s6rAWI1H0jzBlIcC7SF1tL7B6SLADz1kjRgAbnAsDZSwyHs1Nj4UXkgb/7KO?=
 =?us-ascii?Q?NKTPVvw9Mqx85V0OLjHOJT2iblEKlI4iidu2j2XXHtMg+ouVEzOAuB2EtT26?=
 =?us-ascii?Q?N8CPosFBRdjJUX/2lx96YRdlqdpsdfP5Ru6Z9OSy0CEmQr2D2G5hvl+6IYVv?=
 =?us-ascii?Q?mBuCqGmLInUNINN0DBo0/LNtsFSOeD1hzvUzNNsnhlsqcUtFvErg+h0cG4ix?=
 =?us-ascii?Q?pNhiZ7gHu+866tSZKNX1MwIjsHJloSHEPzOM6eZBKTp9dpAyJHcupD/d5zcY?=
 =?us-ascii?Q?WaLhlxTPpWPBBa+DUvSDzeffcLSbOqlyXnQW6k/2T9IvlOFXdspfRdCnVGEv?=
 =?us-ascii?Q?Zjki9uAIY2oe62Hay9l0FpoBp9XoSJ6eZj0f5/Sp975JaCPyBomcUyVmrleL?=
 =?us-ascii?Q?U9f5f2f6wlPg8t2KgK7jK24Gr4GmijSEZQeFXnEHJQhXvqniwzNnbnkbfo07?=
 =?us-ascii?Q?Z6T0J6jMr+1L/X0VQiu2mG1Le9xIFK9jrFgvFr09VwLvlvZgE7qvUvStpg1z?=
 =?us-ascii?Q?21gl0Fdy18b91hpUtu7KaXt9eWCWQJJRzBvKzyxmjRPLJDybgWsf2us5/0X/?=
 =?us-ascii?Q?fFoFB56HYIwSxRzZzJMC3oOVLCXXFJMzOv8C0lAYxw4D2E/wE8CJveWge/IR?=
 =?us-ascii?Q?AfueoVKrKm/3p3ccnh8GcLgTao5O9JCuCAUa9m/62iGbdEYBQMmoaSST9RtA?=
 =?us-ascii?Q?bGtlbBt7w5DEfAXR9QQfk+AN6BEgHBclhy+qFMH4IZeG2WCf42Dqj4M9hfnI?=
 =?us-ascii?Q?9h3qb//mBAY2Yki09C93Pb1Lyj72p1CACf3WFpbF/z+o55mM/Rnp/zW1DqmH?=
 =?us-ascii?Q?Pn11Ww0Q/i++8GnGToNqGr/8n0InUiBk6QrzuaBjSsYR5veJrHpbbL0M3RVM?=
 =?us-ascii?Q?VXV4DNnMGFCc5V7rMlDJz5FMQCJparV7w1pZL+eGkfxRDKmdfPmus4zpotCw?=
 =?us-ascii?Q?4Exz6gbWmKaBf467YM0tHxPGgz74WpWHzRRDuPy/A2S9Vj+mSFo37z5hUJVv?=
 =?us-ascii?Q?wsTmks/LQ5suNyY+dkjJic5lMgr5y2+UQyDx4hTAaT/OgnWPfNKdIPkHuRag?=
 =?us-ascii?Q?L8t496Du3Ugk2puqdZf/rBjfC+Wj8nXPIyrsoJsV7Gagk/bFHX4z/xO4f+pe?=
 =?us-ascii?Q?biHd0SXUBPJoxJ46L7A/MK/nMDYbeH9dRtZ3S+DNRgNTWBTa7t6KyrJgsnu3?=
 =?us-ascii?Q?qhpuxQJ98wxdJM1XnnA=3D?=
X-OriginatorOrg: Nvidia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b2dfa47f-3e3c-4c80-7f1c-08dab09afd0a
X-MS-Exchange-CrossTenant-AuthSource: LV2PR12MB5869.namprd12.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 17 Oct 2022 23:54:54.5399
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 43083d15-7273-40c1-b7db-39efd9ccc17a
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: uvnuN4VTiYtNhPEhV7ueXmToS165rNBS7TU0QTiykD+k6DVqBsli9av7ah/pmf9v
X-MS-Exchange-Transport-CrossTenantHeadersStamped: IA1PR12MB7541
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,
        DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FORGED_SPF_HELO,
        RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_NONE
        autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
        lindbergh.monkeyblade.net
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Oct 17, 2022 at 04:00:29PM -0700, Nicolin Chen wrote:
> This series is to replace the previous EMEDIUMTYPE patch in a VFIO series:
> https://lore.kernel.org/kvm/Yxnt9uQTmbqul5lf@8bytes.org/
> 
> The purpose is to regulate all existing ->attach_dev callback functions to
> use EINVAL exclusively for an incompatibility error between a device and a
> domain. This allows VFIO and IOMMUFD to detect such a soft error, and then
> try a different domain with the same device.
> 
> Among all the patches, the first two are preparatory changes. And then one
> patch to update kdocs and another three patches for the enforcement effort.
> 
> Although it might be ideal to merge the previous VFIO series together with
> this series, given the number of new changes, the review in the IOMMU list
> might need a couple of rounds to finalize. Also, considering that v6.0 is
> at rc5 now, perhaps we could merge this IOMMU series and the VFIO one in
> different cycles to avoid merge conflicts. If there's less concern for it,
> I can respin the finalized version of this series with the previous VFIO
> one to merge together into the VFIO tree.
> 
> This series is also available on Github:
> https://github.com/nicolinc/iommufd/commits/iommu_attach_dev-v7

Since it didn't make v6.1-rc1, I'd like this on a PR as we have two
trees that will need it now.

Joerg I can make this into a formal signed PR if that is how you'd
like things?

Thanks,
Jason