All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Robin Murphy <robin.murphy@arm.com>,
	linux-arch@vger.kernel.org, darren@stevens-zone.net,
	mad skateman <madskateman@gmail.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	iommu@lists.linux-foundation.org,
	Rob Herring <robh+dt@kernel.org>,
	paulus@samba.org, rtd2@xtra.co.nz,
	"contact@a-eon.com" <contact@a-eon.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	nsaenzjulienne@suse.de, Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: Bug 205201 - Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M
Date: Mon, 25 Nov 2019 17:36:17 +0100	[thread overview]
Message-ID: <96537365-8dbf-7f7e-f37f-14bf5c144b45@xenosoft.de> (raw)
In-Reply-To: <20191125073923.GA30168@lst.de>

On 25 November 2019 at 08:39 am, Christoph Hellwig wrote:
> On Sat, Nov 23, 2019 at 12:42:27PM +0100, Christian Zigotzky wrote:
>> Hello Christoph,
>>
>> Please find attached the dmesg of your Git kernel.
> Thanks.  It looks like on your platform the swiotlb buffer isn't
> actually addressable based on the bus dma mask limit, which is rather
> interesting.  swiotlb_init uses memblock_alloc_low to allocate the
> buffer, and I'll need some help from Mike and the powerpc maintainers
> to figure out how that select where to allocate the buffer from, and
> how we can move it to a lower address.  My gut feeling would be to try
> to do what arm64 does and define a new ARCH_LOW_ADDRESS_LIMIT, preferably
> without needing too much arch specific magic.
>
> As a quick hack can you try this patch on top of the tree from Friday?
>
> diff --git a/include/linux/memblock.h b/include/linux/memblock.h
> index f491690d54c6..e3f95c362922 100644
> --- a/include/linux/memblock.h
> +++ b/include/linux/memblock.h
> @@ -344,7 +344,7 @@ static inline int memblock_get_region_node(const struct memblock_region *r)
>   #define MEMBLOCK_LOW_LIMIT 0
>   
>   #ifndef ARCH_LOW_ADDRESS_LIMIT
> -#define ARCH_LOW_ADDRESS_LIMIT  0xffffffffUL
> +#define ARCH_LOW_ADDRESS_LIMIT  0x0fffffffUL
>   #endif
>   
>   phys_addr_t memblock_phys_alloc_range(phys_addr_t size, phys_addr_t align,
>
Hello Christoph,

Thanks a lot for your help! I will test your patch tomorrow.

Cheers,
Christian

WARNING: multiple messages have this Message-ID (diff)
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-arch@vger.kernel.org, darren@stevens-zone.net,
	rtd2@xtra.co.nz, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linux-kernel@vger.kernel.org, Mike Rapoport <rppt@linux.ibm.com>,
	linux-mm@kvack.org, iommu@lists.linux-foundation.org,
	Rob Herring <robh+dt@kernel.org>,
	paulus@samba.org, mad skateman <madskateman@gmail.com>,
	"contact@a-eon.com" <contact@a-eon.com>,
	Robin Murphy <robin.murphy@arm.com>,
	nsaenzjulienne@suse.de
Subject: Re: Bug 205201 - Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M
Date: Mon, 25 Nov 2019 17:36:17 +0100	[thread overview]
Message-ID: <96537365-8dbf-7f7e-f37f-14bf5c144b45@xenosoft.de> (raw)
In-Reply-To: <20191125073923.GA30168@lst.de>

On 25 November 2019 at 08:39 am, Christoph Hellwig wrote:
> On Sat, Nov 23, 2019 at 12:42:27PM +0100, Christian Zigotzky wrote:
>> Hello Christoph,
>>
>> Please find attached the dmesg of your Git kernel.
> Thanks.  It looks like on your platform the swiotlb buffer isn't
> actually addressable based on the bus dma mask limit, which is rather
> interesting.  swiotlb_init uses memblock_alloc_low to allocate the
> buffer, and I'll need some help from Mike and the powerpc maintainers
> to figure out how that select where to allocate the buffer from, and
> how we can move it to a lower address.  My gut feeling would be to try
> to do what arm64 does and define a new ARCH_LOW_ADDRESS_LIMIT, preferably
> without needing too much arch specific magic.
>
> As a quick hack can you try this patch on top of the tree from Friday?
>
> diff --git a/include/linux/memblock.h b/include/linux/memblock.h
> index f491690d54c6..e3f95c362922 100644
> --- a/include/linux/memblock.h
> +++ b/include/linux/memblock.h
> @@ -344,7 +344,7 @@ static inline int memblock_get_region_node(const struct memblock_region *r)
>   #define MEMBLOCK_LOW_LIMIT 0
>   
>   #ifndef ARCH_LOW_ADDRESS_LIMIT
> -#define ARCH_LOW_ADDRESS_LIMIT  0xffffffffUL
> +#define ARCH_LOW_ADDRESS_LIMIT  0x0fffffffUL
>   #endif
>   
>   phys_addr_t memblock_phys_alloc_range(phys_addr_t size, phys_addr_t align,
>
Hello Christoph,

Thanks a lot for your help! I will test your patch tomorrow.

Cheers,
Christian

WARNING: multiple messages have this Message-ID (diff)
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-arch@vger.kernel.org, darren@stevens-zone.net,
	rtd2@xtra.co.nz,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linux-kernel@vger.kernel.org, Mike Rapoport <rppt@linux.ibm.com>,
	linux-mm@kvack.org, iommu@lists.linux-foundation.org,
	Rob Herring <robh+dt@kernel.org>,
	paulus@samba.org, mad skateman <madskateman@gmail.com>,
	"contact@a-eon.com" <contact@a-eon.com>,
	Robin Murphy <robin.murphy@arm.com>,
	nsaenzjulienne@suse.de
Subject: Re: Bug 205201 - Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M
Date: Mon, 25 Nov 2019 17:36:17 +0100	[thread overview]
Message-ID: <96537365-8dbf-7f7e-f37f-14bf5c144b45@xenosoft.de> (raw)
In-Reply-To: <20191125073923.GA30168@lst.de>

On 25 November 2019 at 08:39 am, Christoph Hellwig wrote:
> On Sat, Nov 23, 2019 at 12:42:27PM +0100, Christian Zigotzky wrote:
>> Hello Christoph,
>>
>> Please find attached the dmesg of your Git kernel.
> Thanks.  It looks like on your platform the swiotlb buffer isn't
> actually addressable based on the bus dma mask limit, which is rather
> interesting.  swiotlb_init uses memblock_alloc_low to allocate the
> buffer, and I'll need some help from Mike and the powerpc maintainers
> to figure out how that select where to allocate the buffer from, and
> how we can move it to a lower address.  My gut feeling would be to try
> to do what arm64 does and define a new ARCH_LOW_ADDRESS_LIMIT, preferably
> without needing too much arch specific magic.
>
> As a quick hack can you try this patch on top of the tree from Friday?
>
> diff --git a/include/linux/memblock.h b/include/linux/memblock.h
> index f491690d54c6..e3f95c362922 100644
> --- a/include/linux/memblock.h
> +++ b/include/linux/memblock.h
> @@ -344,7 +344,7 @@ static inline int memblock_get_region_node(const struct memblock_region *r)
>   #define MEMBLOCK_LOW_LIMIT 0
>   
>   #ifndef ARCH_LOW_ADDRESS_LIMIT
> -#define ARCH_LOW_ADDRESS_LIMIT  0xffffffffUL
> +#define ARCH_LOW_ADDRESS_LIMIT  0x0fffffffUL
>   #endif
>   
>   phys_addr_t memblock_phys_alloc_range(phys_addr_t size, phys_addr_t align,
>
Hello Christoph,

Thanks a lot for your help! I will test your patch tomorrow.

Cheers,
Christian
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  parent reply	other threads:[~2019-11-25 16:36 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16  7:06 Bug 205201 - Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M Christian Zigotzky
2019-11-16  7:06 ` Christian Zigotzky
2019-11-21  7:29 ` Christoph Hellwig
2019-11-21  7:29   ` Christoph Hellwig
2019-11-21  7:29   ` Christoph Hellwig
2019-11-21 12:16   ` Christian Zigotzky
2019-11-21 12:16     ` Christian Zigotzky
2019-11-21 12:16     ` Christian Zigotzky
2019-11-21 12:21     ` Christian Zigotzky
2019-11-21 12:21       ` Christian Zigotzky
2019-11-21 12:21       ` Christian Zigotzky
2019-11-21 13:33       ` Robin Murphy
2019-11-21 13:33         ` Robin Murphy
2019-11-21 13:33         ` Robin Murphy
2019-11-21 16:34         ` Christian Zigotzky
2019-11-21 16:34           ` Christian Zigotzky
2019-11-21 16:34           ` Christian Zigotzky
2019-11-21 18:02           ` Christoph Hellwig
2019-11-21 18:02             ` Christoph Hellwig
2019-11-21 18:02             ` Christoph Hellwig
2019-11-21 18:21             ` Christian Zigotzky
2019-11-21 18:21               ` Christian Zigotzky
2019-11-21 18:21               ` Christian Zigotzky
2019-11-23 11:42             ` Christian Zigotzky
2019-11-23 11:42               ` Christian Zigotzky
2019-11-23 11:42               ` Christian Zigotzky
2019-11-25  7:39               ` Christoph Hellwig
2019-11-25  7:39                 ` Christoph Hellwig
2019-11-25  7:39                 ` Christoph Hellwig
2019-11-25  9:32                 ` Mike Rapoport
2019-11-25  9:32                   ` Mike Rapoport
2019-11-25  9:32                   ` Mike Rapoport
2019-11-25  9:32                   ` Mike Rapoport
2019-11-25  9:32                   ` Mike Rapoport
2019-11-25 16:38                   ` Christian Zigotzky
2019-11-25 16:38                     ` Christian Zigotzky
2019-11-25 16:38                     ` Christian Zigotzky
2019-11-26 11:57                   ` Christian Zigotzky
2019-11-26 11:57                     ` Christian Zigotzky
2019-11-26 11:57                     ` Christian Zigotzky
2019-11-25 16:36                 ` Christian Zigotzky [this message]
2019-11-25 16:36                   ` Christian Zigotzky
2019-11-25 16:36                   ` Christian Zigotzky
2019-11-26 11:26                 ` Christian Zigotzky
2019-11-26 11:26                   ` Christian Zigotzky
2019-11-26 11:26                   ` Christian Zigotzky
2019-11-26 16:40                   ` Christoph Hellwig
2019-11-26 16:40                     ` Christoph Hellwig
2019-11-26 16:40                     ` Christoph Hellwig
2019-11-27  6:56                     ` Mike Rapoport
2019-11-27  6:56                       ` Mike Rapoport
2019-11-27  6:56                       ` Mike Rapoport
2019-11-27  6:56                       ` Mike Rapoport
2019-11-27  8:53                       ` Christoph Hellwig
2019-11-27  8:53                         ` Christoph Hellwig
2019-11-27  8:53                         ` Christoph Hellwig
2019-11-27 15:14                       ` Christian Zigotzky
2019-11-27 15:14                         ` Christian Zigotzky
2019-11-27 15:14                         ` Christian Zigotzky
2019-12-04  8:56                       ` Christoph Hellwig
2019-12-04  8:56                         ` Christoph Hellwig
2019-12-04  8:56                         ` Christoph Hellwig
2019-12-04 12:22                         ` Christian Zigotzky
2019-12-04 12:22                           ` Christian Zigotzky
2019-12-04 12:22                           ` Christian Zigotzky
2019-12-04 12:22                           ` Christian Zigotzky
2020-01-10  7:10                         ` Christian Zigotzky
2020-01-10  7:10                           ` Christian Zigotzky
2020-01-10  7:10                           ` Christian Zigotzky
2020-01-15 15:18                           ` Christoph Hellwig
2020-01-15 15:18                             ` Christoph Hellwig
2020-01-15 15:18                             ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2019-10-29  4:49 Christian Zigotzky
2019-10-30  0:10 ` Christian Zigotzky

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=96537365-8dbf-7f7e-f37f-14bf5c144b45@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=benh@kernel.crashing.org \
    --cc=contact@a-eon.com \
    --cc=darren@stevens-zone.net \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=paulus@samba.org \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=rppt@linux.ibm.com \
    --cc=rtd2@xtra.co.nz \
    /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.