From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [PATCH V4 05/18] iommu/ioasid: Redefine IOASID set and allocation APIs Date: Fri, 7 May 2021 14:10:50 -0300 Message-ID: <20210507171050.GV1370958@nvidia.com> References: <20210422121020.GT1370958@nvidia.com> <20210423114944.GF1370958@nvidia.com> <20210426123817.GQ1370958@nvidia.com> <20210428090625.5a05dae8@redhat.com> <20210507110614.7b8e6998@redhat.com> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Nvidia.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=M0MLvbZBevsyhRA6EvN0IFIo7lI5yPAeclzQDtJqH28=; b=Ivs88zu21G2JnEM1a7qfGSMjdOynDrACqWCDOh0WSfiQMwQybGgE4iBH2jGuw2z7VP0MibFxOUVJB2xivbgOnG6qdBMV5neroDXfKi+FODxjcCLI47cT1mSn7+V/RsOnYBBrpSJkK/rjVEN6x+aDVdbadoVhCVqgpWpclx7XRyQeJDjSPjTPOPB4VMAXwLqcEwZNSNLc9RCnICOPtj9EctWBCExpWfB/qR+x6mmNn0isNeDeM/cQRb7PsgWF5UPtM+NzYCh4bIwQwQmn/QxnDklVsyiwi/jzN7MBoa6dZNR1eDHVzIn7AAmVJ+z9ts1jVSu18xvroB1siJNcdmqMLA== Content-Disposition: inline In-Reply-To: <20210507110614.7b8e6998-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Alex Williamson Cc: "Tian, Kevin" , "Liu, Yi L" , Jacob Pan , Auger Eric , Jean-Philippe Brucker , LKML , Joerg Roedel , Lu Baolu , David Woodhouse , "iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org" , "cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Tejun Heo , Li Zefan , Johannes Weiner , Jean-Philippe Brucker , Jonathan Corbet , "Raj, Ashok" , "Wu, Hao" , "Jiang, Dave" On Fri, May 07, 2021 at 11:06:14AM -0600, Alex Williamson wrote: > We had tossed around an idea of a super-container with vfio, it's maybe > something we'd want to incorporate into this design. For instance, if > memory could be pre-registered with a super container, which would > handle the locked memory accounting for that memory, then > sub-containers could all handle the IOMMU context of their sets of > devices relative to that common memory pool. This is where I suggested to David to use nesting of IOASIDs. Without HW support for nesting a SW nest is really just re-using the memory registration information stored in the parent when constructing the children Jason