On Thu Dec 05 19, Lu Baolu wrote:
Hi,
On 12/5/19 10:25 AM, Jerry Snitselaar wrote:
It seems that iommu pci bus probe didn't enumerate device [01:00.2] and
[02:00.0], the corresponding context entries were not setup. Hence dma
fault generated when devices access the memory.
Do these two
Hi,
On 12/5/19 10:25 AM, Jerry Snitselaar wrote:
It seems that iommu pci bus probe didn't enumerate device [01:00.2] and
[02:00.0], the corresponding context entries were not setup. Hence dma
fault generated when devices access the memory.
Do these two devices show in "lspci" output? How do
On Thu Dec 05 19, Lu Baolu wrote:
Hi,
On 12/5/19 4:53 AM, Jerry Snitselaar wrote:
Attaching console output (can't get to a point to actually log in) and
config that is used to build that kernel.
[...]
[ 21.969477] pci :00:00.0: Adding to iommu group 0
[ 21.971390] pci :00:01.0:
Hi,
On 12/5/19 4:53 AM, Jerry Snitselaar wrote:
Attaching console output (can't get to a point to actually log in) and
config that is used to build that kernel.
[...]
[ 21.969477] pci :00:00.0: Adding to iommu group 0
[ 21.971390] pci :00:01.0: Adding to iommu group 1
[
Hi,
On 12/3/19 7:47 PM, Nicolas Saenz Julienne wrote:
Some users need to make sure their rounding function accepts and returns
64bit long variables regardless of the architecture. Sadly
roundup/rounddown_pow_two() takes and returns unsigned longs. It turns
out ilog2() already handles 32/64bit
On Wed, Dec 4, 2019 at 7:56 AM Robin Murphy wrote:
>
> On 22/11/2019 11:31 pm, Jordan Crouse wrote:
> > Add a compatible string to identify SMMUs that are attached
> > to Adreno GPU devices that wish to support split pagetables.
>
> A software policy decision is not, in itself, a good
On Wed, 4 Dec 2019 08:32:17 +0800
Lu Baolu wrote:
> Hi Jacob,
>
> On 12/4/19 12:50 AM, Jacob Pan wrote:
> > On Tue, 3 Dec 2019 10:44:45 +0800
> > Lu Baolu wrote:
> >
> >> Hi Jacob,
> >>
> >> On 12/3/19 4:02 AM, Jacob Pan wrote:
> >>> On Fri, 22 Nov 2019 11:04:44 +0800
> >>> Lu Baolu
From: Mike Rapoport
Some powerpc platforms (e.g. 85xx) limit DMA-able memory way below 4G. If a
system has more physical memory than this limit, the swiotlb buffer is not
addressable because it is allocated from memblock using top-down mode.
Force memblock to bottom-up mode before calling
For the changes under drivers/net/ethernet/sfc:
Reviewed-by: Martin Habets
On 03/12/2019 11:47, Nicolas Saenz Julienne wrote:
> Some users need to make sure their rounding function accepts and returns
> 64bit long variables regardless of the architecture. Sadly
> roundup/rounddown_pow_two()
On 22/11/2019 11:31 pm, Jordan Crouse wrote:
Add implementation specific support to enable split pagetables for
SMMU implementations attached to Adreno GPUs on Qualcomm targets.
To enable split pagetables the driver will set an attribute on the domain.
if conditions are correct, set up the
> -Original Message-
> From: Deucher, Alexander
> Sent: Monday, December 2, 2019 11:37 AM
> To: Lucas Stach ; Kai-Heng Feng
> ; j...@8bytes.org; Koenig, Christian
> (christian.koe...@amd.com)
> Cc: iommu@lists.linux-foundation.org; linux-ker...@vger.kernel.org
> Subject: RE: [PATCH v2]
On 22/11/2019 11:31 pm, Jordan Crouse wrote:
Add a compatible string to identify SMMUs that are attached
to Adreno GPU devices that wish to support split pagetables.
A software policy decision is not, in itself, a good justification for a
DT property. Is the GPU SMMU fundamentally different
On Wed, Dec 04, 2019 at 02:35:24PM +0200, Mike Rapoport wrote:
> From: Mike Rapoport
>
> Some powerpc platforms (e.g. 85xx) limit DMA-able memory way below 4G. If a
> system has more physical memory than this limit, the swiotlb buffer is not
> addressable because it is allocated from memblock
Devices that are forced to DMA through swiotlb need to be treated as if
they are addressing limited.
Signed-off-by: Christoph Hellwig
---
include/linux/dma-direct.h | 1 +
kernel/dma/direct.c| 8 ++--
kernel/dma/mapping.c | 3 +++
3 files changed, 10 insertions(+), 2
Hi all,
this little series fixes dma_addressing_limited to return true for
systems that use bounce buffers due to memory encryption.
Changes since v1:
- take SWIOTLB_FORCE into account
___
iommu mailing list
iommu@lists.linux-foundation.org
This function isn't used in the fast path, and moving it out of line
will reduce include clutter with the next change.
Signed-off-by: Christoph Hellwig
---
include/linux/dma-mapping.h | 14 +-
kernel/dma/mapping.c| 15 +++
2 files changed, 16 insertions(+), 13
I think we have to wait to Roland’s test results with his SCSI PCI card.
Christian
Sent from my iPhone
> On 4. Dec 2019, at 09:56, Christoph Hellwig wrote:
>
>> On Wed, Nov 27, 2019 at 08:56:25AM +0200, Mike Rapoport wrote:
>>> On Tue, Nov 26, 2019 at 05:40:26PM +0100, Christoph Hellwig
On Wed, Nov 27, 2019 at 08:56:25AM +0200, Mike Rapoport wrote:
> On Tue, Nov 26, 2019 at 05:40:26PM +0100, Christoph Hellwig wrote:
> > On Tue, Nov 26, 2019 at 12:26:38PM +0100, Christian Zigotzky wrote:
> > > Hello Christoph,
> > >
> > > The PCI TV card works with your patch! I was able to patch
18 matches
Mail list logo
