From: Michael Ellerman <mpe@ellerman.id.au>
To: Gaurav Batra <gbatra@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, brking@linux.vnet.ibm.com,
gjoyce@linux.vnet.ibm.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device
Date: Fri, 27 Oct 2023 20:59:56 +1100 [thread overview]
Message-ID: <169840079678.2701453.14213017318168478377.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20231003030802.47914-1-gbatra@linux.vnet.ibm.com>
On Mon, 02 Oct 2023 22:08:02 -0500, Gaurav Batra wrote:
> When a device is initialized, the driver invokes dma_supported() twice -
> first for streaming mappings followed by coherent mappings. For an
> SR-IOV device, default window is deleted and DDW created. With vPMEM
> enabled, TCE mappings are dynamically created for both vPMEM and SR-IOV
> device. There are no direct mappings.
>
> First time when dma_supported() is called with 64 bit mask, DDW is created
> and marked as dynamic window. The second time dma_supported() is called,
> enable_ddw() finds existing window for the device and incorrectly returns
> it as "direct mapping".
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device
https://git.kernel.org/powerpc/c/3bf983e4e93ce8e6d69e9d63f52a66ec0856672e
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Gaurav Batra <gbatra@linux.vnet.ibm.com>
Cc: brking@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
stable@vger.kernel.org, gjoyce@linux.vnet.ibm.com
Subject: Re: [PATCH v2] powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device
Date: Fri, 27 Oct 2023 20:59:56 +1100 [thread overview]
Message-ID: <169840079678.2701453.14213017318168478377.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20231003030802.47914-1-gbatra@linux.vnet.ibm.com>
On Mon, 02 Oct 2023 22:08:02 -0500, Gaurav Batra wrote:
> When a device is initialized, the driver invokes dma_supported() twice -
> first for streaming mappings followed by coherent mappings. For an
> SR-IOV device, default window is deleted and DDW created. With vPMEM
> enabled, TCE mappings are dynamically created for both vPMEM and SR-IOV
> device. There are no direct mappings.
>
> First time when dma_supported() is called with 64 bit mask, DDW is created
> and marked as dynamic window. The second time dma_supported() is called,
> enable_ddw() finds existing window for the device and incorrectly returns
> it as "direct mapping".
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device
https://git.kernel.org/powerpc/c/3bf983e4e93ce8e6d69e9d63f52a66ec0856672e
cheers
next prev parent reply other threads:[~2023-10-27 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 3:08 [PATCH v2] powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device Gaurav Batra
2023-10-03 3:08 ` Gaurav Batra
2023-10-27 9:59 ` Michael Ellerman [this message]
2023-10-27 9:59 ` Michael Ellerman
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=169840079678.2701453.14213017318168478377.b4-ty@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=brking@linux.vnet.ibm.com \
--cc=gbatra@linux.vnet.ibm.com \
--cc=gjoyce@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@vger.kernel.org \
/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.