Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1266654

Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails

From Sinan Kaya <okaya@codeaurora.org>
Newsgroups linux.kernel
Subject Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails
Date 2015-11-10 18:20 +0100
Message-ID <qtkKn-7Wr-19@gated-at.bofh.it> (permalink)
References <qsJUu-88f-9@gated-at.bofh.it> <qtcMO-2IH-5@gated-at.bofh.it> <qtjEC-7hv-1@gated-at.bofh.it> <qtkhj-7vy-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw



On 11/10/2015 11:47 AM, Arnd Bergmann wrote:
> On Tuesday 10 November 2015 11:06:40 Sinan Kaya wrote:
>> On 11/10/2015 3:38 AM, Arnd Bergmann wrote:
>>   > No, as Timur found, the driver is correct and it intentionally
>>> sets the 32-bit mask, and that is guaranteed to work on all sane
>>> hardware. Don't change the driver but find a better platform for
>>> your workload, or talk to the people that are responsible for
>>> the platform and get them to fix it.
>>
>> Platform does have an IOMMU. No issues there. I am trying to clean out
>> the patch pipe I have in order to get this card working with and without
>> IOMMU.
>
> On PowerPC, I think we automatically enable the IOMMU whenever a DMA
> mask is set that doesn't cover all of the RAM. We could think about
> doing the same thing on ARM64 to make all devices work out of the box.
>

The ACPI IORT table declares whether you enable IOMMU for a particular 
device or not. The placement of IOMMU HW is system specific. The IORT 
table gives the IOMMU HW topology to the operating system.

>>> If the platform also doesn't have an IOMMU, you can probably work
>>> around it by setting up the dma-ranges property of the PCI host
>>> to map the low PCI addresses to the start of RAM. This will also
>>> require changes in the bootloader to set up the PCI outbound translation,
>>> and it will require implementing the DMA offset on ARM64, which I was
>>> hoping to avoid.
>>
>>   From the email thread, it looks like this was introduced to support
>> some legacy card that has 64 bit addressing limitations and is being
>> carried around ("rotted") since then.
>>
>> I'm the second guy after the powerpc architecture complaining about the
>> very same issue. Any red flags?
>
> What BenH was worried about here is that the driver sets different masks
> for streaming and coherent mappings, which is indeed a worry that
> could hit us on ARM as well, but I suppose we'll have to deal with
> that in platform code.
>
> Setting both masks to 32-bit is something that a lot of drivers do,
> and without IOMMU enabled, you'd hit the same bug on all of them.
>

Maybe, maybe not. This is the only card that I had problems with.

>> I can't change the address map for PCIe. SBSA requires all inbound PCIe
>> addresses to be non-translated.
>
> What about changing the memory map? I suspect there will be more
> problems for you in the future when all of your RAM is at high
> addresses.  Is this something you could fix in the bootloader by
> moving the first 2GB to a different CPU physical address?

I'm thinking about this.

>
>> I'll just have to stick with IOMMU for this card.
>
> Ok. But how do you currently decide whether to use the IOMMU or not?
>

ACPI table. I wanted to get this fix in so that all operating systems 
whether they have IOMMU driver enabled or not would work.

> 	Arnd
>

-- 
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a 
Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-09 03:00 +0100
  Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Hannes Reinecke <hare@suse.de> - 2015-11-09 08:20 +0100
    Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Arnd Bergmann <arnd@arndb.de> - 2015-11-09 10:10 +0100
      Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-09 15:10 +0100
        Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Arnd Bergmann <arnd@arndb.de> - 2015-11-09 15:40 +0100
          Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Timur Tabi <timur@codeaurora.org> - 2015-11-10 00:30 +0100
          Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-10 00:30 +0100
            Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Arnd Bergmann <arnd@arndb.de> - 2015-11-10 09:50 +0100
              Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-10 17:10 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Arnd Bergmann <arnd@arndb.de> - 2015-11-10 17:50 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Timur Tabi <timur@codeaurora.org> - 2015-11-10 18:10 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Arnd Bergmann <arnd@arndb.de> - 2015-11-10 20:20 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Timur Tabi <timur@codeaurora.org> - 2015-11-10 22:10 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Timur Tabi <timur@codeaurora.org> - 2015-11-10 23:00 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Arnd Bergmann <arnd@arndb.de> - 2015-11-10 23:10 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Arnd Bergmann <arnd@arndb.de> - 2015-11-10 23:00 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-10 18:20 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails James Bottomley <James.Bottomley@HansenPartnership.com> - 2015-11-10 19:30 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-10 20:20 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails James Bottomley <James.Bottomley@HansenPartnership.com> - 2015-11-10 20:50 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-10 21:00 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails James Bottomley <James.Bottomley@HansenPartnership.com> - 2015-11-10 21:10 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-10 21:30 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails James Bottomley <James.Bottomley@HansenPartnership.com> - 2015-11-10 21:40 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Arnd Bergmann <arnd@arndb.de> - 2015-11-10 21:00 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-10 22:00 +0100
                Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Arnd Bergmann <arnd@arndb.de> - 2015-11-10 23:10 +0100
    Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA  fails Sinan Kaya <okaya@codeaurora.org> - 2015-11-09 15:10 +0100

csiph-web