All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Steven Sistare <steven.sistare@oracle.com>
Cc: iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
	Nicolin Chen <nicolinc@nvidia.com>
Subject: Re: [PATCH V1 2/9] iommufd: remove uptr from iopt_alloc_iova
Date: Tue, 24 Sep 2024 16:50:52 -0300	[thread overview]
Message-ID: <20240924195052.GN9417@nvidia.com> (raw)
In-Reply-To: <70cd1f1f-95a1-48ee-a5cd-97a5769a1210@oracle.com>

On Wed, Sep 18, 2024 at 10:51:32AM -0400, Steven Sistare wrote:
> On 9/15/2024 4:41 PM, Jason Gunthorpe wrote:
> > On Sat, Sep 14, 2024 at 06:05:51AM -0700, Steve Sistare wrote:
> > > iopt_alloc_iova takes a uptr argument but only checks for its alignment.
> > > Pass an offset from start instead to eliminate its dependence on a user
> > > address.
> > 
> > An offset from start is a meaningfully different thing for this, it
> > throws away all the information it is trying to extract (is the uptr
> > huge page aligned)
> 
> Interpret offset as "from the start of the address space, eg 0" and it
> works. That was my intent, since I pass offset from the start of the file
> address space in a subsequent patch.  But instead, I can rename uptr to
> to address and describe it this way:
> 
>   iopt_alloc_iova takes a uptr argument but only checks for its alignment.
>   Generalize this to an unsigned address, which will be the offset from the
>   start of a file in a subsequent patch.  No functional change.

Yes that makes sense

Jason

  reply	other threads:[~2024-09-24 19:50 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14 13:05 [PATCH V1 0/9] iommu_ioas_map_file Steve Sistare
2024-09-14 13:05 ` [PATCH V1 1/9] mm/gup: repin_folio_unhugely Steve Sistare
2024-09-14 13:19   ` Steven Sistare
2024-09-17 12:25     ` David Hildenbrand
2024-09-18 14:51       ` Steven Sistare
2024-09-19  8:11         ` David Hildenbrand
2024-09-19 21:06           ` Steven Sistare
2024-09-26 11:38             ` David Hildenbrand
2024-09-20 13:28           ` Jason Gunthorpe
2024-09-26 11:32             ` David Hildenbrand
2024-09-26 11:40               ` Jason Gunthorpe
2024-09-26 12:57                 ` David Hildenbrand
2024-09-26 12:58                   ` David Hildenbrand
2024-09-15 20:37   ` Jason Gunthorpe
2024-09-18 14:51     ` Steven Sistare
2024-09-14 13:05 ` [PATCH V1 2/9] iommufd: remove uptr from iopt_alloc_iova Steve Sistare
2024-09-15 20:41   ` Jason Gunthorpe
2024-09-18 14:51     ` Steven Sistare
2024-09-24 19:50       ` Jason Gunthorpe [this message]
2024-09-14 13:05 ` [PATCH V1 3/9] iommufd: generalize iopt_pages address Steve Sistare
2024-09-18 14:52   ` Steven Sistare
2024-09-14 13:05 ` [PATCH V1 4/9] iommufd: pfn reader for file mappings Steve Sistare
2024-09-15 20:51   ` Jason Gunthorpe
2024-09-18 14:51     ` Steven Sistare
2024-09-14 13:05 ` [PATCH V1 5/9] iommufd: IOMMU_IOAS_MAP_FILE interface Steve Sistare
2024-09-15 20:52   ` Jason Gunthorpe
2024-09-18 14:51     ` Steven Sistare
2024-09-14 13:05 ` [PATCH V1 6/9] iommufd: IOMMU_IOAS_MAP_FILE implementation Steve Sistare
2024-09-17  1:48   ` kernel test robot
2024-09-14 13:05 ` [PATCH V1 7/9] iommufd: file mappings for mdev Steve Sistare
2024-09-18 14:52   ` Steven Sistare
2024-09-14 13:05 ` [PATCH V1 8/9] iommufd: replace upages_len Steve Sistare
2024-09-14 13:05 ` [PATCH V1 9/9] iommufd: optimize file mapping Steve Sistare
2024-09-15 20:59   ` Jason Gunthorpe
2024-09-18 14:52     ` Steven Sistare
2024-09-14 13:21 ` [PATCH V1 0/9] iommu_ioas_map_file Steven Sistare
2024-09-15 20:30 ` Jason Gunthorpe
2024-09-18 14:52   ` Steven Sistare
2024-09-23 17:33     ` Jason Gunthorpe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240924195052.GN9417@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=kevin.tian@intel.com \
    --cc=nicolinc@nvidia.com \
    --cc=steven.sistare@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.