Date:   Fri, 10 Mar 2023 13:03:47 -0400
From:   Jason Gunthorpe <jgg@nvidia.com>
To:     Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc:     Eric Auger <eric.auger@redhat.com>,
        Nicolin Chen <nicolinc@nvidia.com>,
        "robin.murphy@arm.com" <robin.murphy@arm.com>,
        "will@kernel.org" <will@kernel.org>,
        "kevin.tian@intel.com" <kevin.tian@intel.com>,
        "baolu.lu@linux.intel.com" <baolu.lu@linux.intel.com>,
        "joro@8bytes.org" <joro@8bytes.org>,
        "jean-philippe@linaro.org" <jean-philippe@linaro.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "iommu@lists.linux.dev" <iommu@lists.linux.dev>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 01/14] iommu: Add iommu_get_unmanaged_domain helper
Message-ID: <ZAti8wy9wXwtIqLT@nvidia.com>
References: <cover.1678348754.git.nicolinc@nvidia.com>
 <9b1077601cace998533129327f5e7ad946752d29.1678348754.git.nicolinc@nvidia.com>
 <eddde530-cd37-f493-7f0f-c97905f0de64@redhat.com>
 <ZAtNrFAEHvmM4FOW@nvidia.com>
 <f61ca5693d8845eba0a2139324e52d98@huawei.com>
 <ZAtTNK1NbMJ4iyE0@nvidia.com>
 <b9e850a91c494a5397a0ae154e9ef1da@huawei.com>
 <ZAtY8S53//5P5egd@nvidia.com>
 <ba7f4b9f81264832842a6c7486cb6dd7@huawei.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ba7f4b9f81264832842a6c7486cb6dd7@huawei.com>
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?NQe+cRxYQz0dkeoztbJBDuCkoO12Z8dHDEjc9GiWLUSzX+6x4Njk7va2sCFG?=
 =?us-ascii?Q?mccyuG5NVHjgXWVBpLQwYzDakIG0+oF2TCPNCdeulu9zzPVnyq/ufEZR0Mmy?=
 =?us-ascii?Q?mVsG5SN1f82i5mx10f3jpRoOL+yGc81DgO43ZOXf74O9sW7n0478EleG90K6?=
 =?us-ascii?Q?o5LoshrtJhAauNzQhoZxiyzvz8comReXoYICIqZvI57p+aHHeNe24t6Z+Hlh?=
 =?us-ascii?Q?Ua/SyNT4rAWfdHaZV5pgo8KAct8ZQrjMgKWfxsTPFvpQCrv1+Dv24BvOEjl/?=
 =?us-ascii?Q?T7j0gLcoG6u/+hW5BcqMmFDxKZg1lyzEdJ+QyVWNfwg0MPc77sJLIqB6S/mz?=
 =?us-ascii?Q?Ju9ocStdEXkEJTRLzRTyptOqbDoADfC3864PNYZWbbq8GhvG037K9CA1Ruez?=
 =?us-ascii?Q?3rJ8xlMUOMXKDAIzSU716bGHM/zM3z3BXQJ38NAc0krTuONLl1kFmNLBsy0Y?=
 =?us-ascii?Q?iI5itYEqbsvivkEFtabGLpJZL9NghjREteZAUI7Y0dspzwb2ujDHBs/3xMh3?=
 =?us-ascii?Q?UoNmIATbRHxqo194wNxz5Ze/2sz5QV6a9MOcR4rYpU3wOmYlY+Zi5ZQAYk1x?=
 =?us-ascii?Q?J9ZjMqY6YWxow9eMv7ua4m5ZBO4AbqhMqcosfzRvywl4tiYLgDjVV2M90T8x?=
 =?us-ascii?Q?RSNWMksA+Xi8t8Vuy1FYW/8hmxhUqtVlMWxeeNigFUGs9oNPZDSA5n11g2Kl?=
 =?us-ascii?Q?f3bEQTeh8MGaAHLqXFxod8WYw570x5+Pqd4bIIQxxR2iV9epq3Ew9rHqtFq/?=
 =?us-ascii?Q?8j0kJhXHlAQ+9yXLjQnbxPlEj728WP4trkQKLYECqTaVXGPUdinYqDBiv/UE?=
 =?us-ascii?Q?FhB2k8IwWKadSiHZE+K19lPVdp3rk76O5VBkn2sFIE6j0g7Y9qbJjKuB/mEH?=
 =?us-ascii?Q?rkXxlbznbHx4e79ODh43ETVZHcaOFoPvF0oMEX6mEnqaUyDroHQNjeZ2p35E?=
 =?us-ascii?Q?5n9gSgbiGhNUlZQBghPTGPt8riM0MxCRe9anMZdZ3YvPcH+j9rACH+Y03alb?=
 =?us-ascii?Q?TnJoVhwf9Tby7+k9i9cKOA9EeT7CpVeTiSiRGt+naCR3IES0keaYvpPaJPWh?=
 =?us-ascii?Q?AKYRKENxx/4O2J0StgfEs3RVaouRaqsZm7a2OxFbNqP0Fxgzx03AfJJpSZ3k?=
 =?us-ascii?Q?mYelJovzgXQGIEIP0gES2o4QHzu+bBGs83XnTU2goS7sO+wZoexRlt+EJkNW?=
 =?us-ascii?Q?S1psiYUYJkWbL+Lx9W6nkNqVQe/GnT0hpskK2SddCLMEqLeZQi0iKG/hbHIy?=
 =?us-ascii?Q?eY375vN2AwQxiz8j+rA80bMUZ4uSFv6xJDLFb8tI8lxxpW4Tnir0ifdr07cV?=
 =?us-ascii?Q?rwH0qZMCCgrby+x5WVgQ3N8SVtJoKEwRITPXiuXXMz7JERYR7IkP7ErPbfny?=
 =?us-ascii?Q?PyTED2Yw6b4d4ve4DCfJxsWwbn7ww8b9EckXZH/8DTxH6OlsHu8iYz4YnVSD?=
 =?us-ascii?Q?2Ojqyqg9tIfBblHTTBBICBhvoFGzexOIVgfJhKv1eDNDIIY0PNk8R3mlJQK/?=
 =?us-ascii?Q?aZYcsKMFuqj5WUUAZXNoaw68Rw5iHWjIkFT/dxYIz3jtK/rQCe/xFJvLe3o0?=
 =?us-ascii?Q?3XwT8XvXSBmPlf9vNLt8ymzalo9HZcnVnXZVEINk?=
X-OriginatorOrg: Nvidia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 36ba5026-367c-4f22-2016-08db21896b9b
X-MS-Exchange-CrossTenant-AuthSource: LV2PR12MB5869.namprd12.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Mar 2023 17:03:50.4652
 (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: EOiDvzpad0easxF1igdp8divV+MYRjwY+vq4ZarXwXtq0RfI1TEVl6gTZuDbs7TY
X-MS-Exchange-Transport-CrossTenantHeadersStamped: IA1PR12MB8495
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Mar 10, 2023 at 04:30:03PM +0000, Shameerali Kolothum Thodi wrote:
> 
> 
> > -----Original Message-----
> > From: Jason Gunthorpe [mailto:jgg@nvidia.com]
> > Sent: 10 March 2023 16:21
> > To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> > Cc: Eric Auger <eric.auger@redhat.com>; Nicolin Chen
> > <nicolinc@nvidia.com>; robin.murphy@arm.com; will@kernel.org;
> > kevin.tian@intel.com; baolu.lu@linux.intel.com; joro@8bytes.org;
> > jean-philippe@linaro.org; linux-arm-kernel@lists.infradead.org;
> > iommu@lists.linux.dev; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH v1 01/14] iommu: Add iommu_get_unmanaged_domain
> > helper
> > 
> > On Fri, Mar 10, 2023 at 04:07:38PM +0000, Shameerali Kolothum Thodi
> > wrote:
> > > >
> > https://lore.kernel.org/linux-arm-kernel/20220420164836.1181-5-shameer
> > > > > ali.kolothum.thodi@huawei.com/
> > > >
> > > > So "boot configration" is more like "don't change the RIDs"? Ie don't
> > enable
> > > > SRIOV?
> > >
> > > Yes. Don't think it will work with SR-IOV if you can't guarantee the RMR
> > specified
> > > SID.
> > 
> > So I think we are probably good them because vSR-IOV is already not
> > supported by qemu, so it impossible for a VM to change the PCI
> > configuration in a way that would alter the RID to SID mapping?
> > 
> 
> Provided we fix the issue mentioned by Eric. This was discussed here previously,
> 
> https://lore.kernel.org/linux-arm-kernel/bb3688c7-8f42-039e-e22f-6529078da97d@redhat.com/

Ah, I see so that we don't renumber the buses during PCI discovery..

It seems like Eric's issue is overly broad if we just want to block
RID reassignment that doesn't impact MMIO layout.

But, still, why do we care about this?

The vIOMMU should virtualize the vSIDs right? So why does qemu give a
vSID list to the guest anyhow? Shouldn't the guest use an algorithmic
calculation from the vRID so that qemu can reverse it to the correct
vPCI device and thus the correct vfio_device and then dev id in the
iommu_domain?

Jason