Linux IOMMU Development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: thierry.reding@gmail.com, robin.murphy@arm.com,
	iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] iommu: map reserved memory as cacheable if device is coherent
Date: Wed, 26 Jul 2023 09:32:22 -0300	[thread overview]
Message-ID: <ZMESVmkUUshDzlbp@ziepe.ca> (raw)
In-Reply-To: <c1c1f3d2-61c1-c1da-36d8-900f1982db63@nxp.com>

On Wed, Jul 26, 2023 at 03:29:47PM +0300, Laurentiu Tudor wrote:
> 
> 
> On 7/26/2023 3:22 PM, Jason Gunthorpe wrote:
> > On Tue, Jul 25, 2023 at 05:00:55PM +0300, laurentiu.tudor@nxp.com wrote:
> > > From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
> > > 
> > > Check if the device is marked as DMA coherent in the DT and if so,
> > > map its reserved memory as cacheable in the IOMMU.
> > > 
> > > Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com>
> > > ---
> > >   drivers/iommu/of_iommu.c | 3 +++
> > >   1 file changed, 3 insertions(+)
> > 
> > This only makes sense for IOMMU_RESV_DIRECT - is that your use case?
> > Maybe mention that in the commit message
> 
> Yep. Will respin with an improved commit message.
> 
> > And add a fixes for the commit that introduces IOMMU_RESV_DIRECT into
> > of_iommu.c
> 
> Would it make more sense to mention the commit [1] that actually added this
> support for mapping reserved memory in IOMMU?
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a5bf3cfce8cb77d9d24613ab52d520896f83dd48

Yes, that should be marked Fixes: - it added IOMMU_RESV_DIRECT without
forming the PROT properly

Jason

      reply	other threads:[~2023-07-26 12:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 14:00 [RFC PATCH] iommu: map reserved memory as cacheable if device is coherent laurentiu.tudor
2023-07-26 12:22 ` Jason Gunthorpe
2023-07-26 12:29   ` Laurentiu Tudor
2023-07-26 12:32     ` Jason Gunthorpe [this message]

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=ZMESVmkUUshDzlbp@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=iommu@lists.linux.dev \
    --cc=laurentiu.tudor@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox