From: Christoph Hellwig <hch@lst.de>
To: Mike Rapoport <rppt@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Conor.Dooley@microchip.com, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: linux-next: Tree for May 3
Date: Wed, 11 May 2022 16:10:34 +0200 [thread overview]
Message-ID: <20220511141034.GA31732@lst.de> (raw)
In-Reply-To: <YnvDdPz4S5IJ7l/5@kernel.org>
On Wed, May 11, 2022 at 05:08:52PM +0300, Mike Rapoport wrote:
> I guess the default to use memblock_alloc_low() backfires on system with
> physical memory living at 0x1000200000:
>
> [ 0.000000] Early memory node ranges
> [ 0.000000] node 0: [mem 0x0000001000200000-0x000000103fffffff]
>
> The default limit for "low" memory is 0xffffffff and there is simply no
> memory there.
Is there any way to ask memblock for a specific address limit?
swiotlb just wants <= 32-bit by default. With the little caveat
that it should be 32-bit addressable for all devices, and we don't
know the physical to dma address mapping at time of allocation.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mike Rapoport <rppt@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Conor.Dooley@microchip.com, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: linux-next: Tree for May 3
Date: Wed, 11 May 2022 16:10:34 +0200 [thread overview]
Message-ID: <20220511141034.GA31732@lst.de> (raw)
In-Reply-To: <YnvDdPz4S5IJ7l/5@kernel.org>
On Wed, May 11, 2022 at 05:08:52PM +0300, Mike Rapoport wrote:
> I guess the default to use memblock_alloc_low() backfires on system with
> physical memory living at 0x1000200000:
>
> [ 0.000000] Early memory node ranges
> [ 0.000000] node 0: [mem 0x0000001000200000-0x000000103fffffff]
>
> The default limit for "low" memory is 0xffffffff and there is simply no
> memory there.
Is there any way to ask memblock for a specific address limit?
swiotlb just wants <= 32-bit by default. With the little caveat
that it should be 32-bit addressable for all devices, and we don't
know the physical to dma address mapping at time of allocation.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-05-11 14:10 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 7:29 linux-next: Tree for May 3 Stephen Rothwell
2022-05-04 8:32 ` Conor.Dooley
2022-05-04 8:32 ` Conor.Dooley
2022-05-09 13:33 ` Conor.Dooley
2022-05-09 13:33 ` Conor.Dooley
2022-05-09 14:11 ` Christoph Hellwig
2022-05-09 14:11 ` Christoph Hellwig
2022-05-09 14:39 ` Conor.Dooley
2022-05-09 14:39 ` Conor.Dooley
2022-05-10 11:20 ` Conor.Dooley
2022-05-10 11:20 ` Conor.Dooley
2022-05-11 6:22 ` Christoph Hellwig
2022-05-11 6:22 ` Christoph Hellwig
2022-05-11 6:44 ` Conor.Dooley
2022-05-11 6:44 ` Conor.Dooley
2022-05-11 6:48 ` Christoph Hellwig
2022-05-11 6:48 ` Christoph Hellwig
2022-05-11 10:10 ` Conor.Dooley
2022-05-11 10:10 ` Conor.Dooley
2022-05-11 12:37 ` Christoph Hellwig
2022-05-11 12:37 ` Christoph Hellwig
2022-05-11 14:08 ` Mike Rapoport
2022-05-11 14:08 ` Mike Rapoport
2022-05-11 14:10 ` Christoph Hellwig [this message]
2022-05-11 14:10 ` Christoph Hellwig
2022-05-11 14:37 ` Mike Rapoport
2022-05-11 14:37 ` Mike Rapoport
2022-05-11 14:40 ` Christoph Hellwig
2022-05-11 14:40 ` Christoph Hellwig
2022-05-13 7:55 ` Conor.Dooley
2022-05-13 7:55 ` Conor.Dooley
2022-05-14 12:18 ` Geert Uytterhoeven
2022-05-14 12:18 ` Geert Uytterhoeven
2022-05-16 9:47 ` Conor.Dooley
2022-05-16 9:47 ` Conor.Dooley
-- strict thread matches above, loose matches on Subject: below --
2024-05-03 7:17 Stephen Rothwell
2021-05-03 2:59 Stephen Rothwell
2019-05-03 10:00 Stephen Rothwell
2018-05-03 5:13 Stephen Rothwell
2017-05-03 5:54 Stephen Rothwell
2016-05-03 9:37 Stephen Rothwell
2013-05-03 4:10 Stephen Rothwell
2013-05-03 4:10 ` Stephen Rothwell
2012-05-03 6:38 Stephen Rothwell
2011-05-03 5:47 Stephen Rothwell
2010-05-03 5:16 Stephen Rothwell
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=20220511141034.GA31732@lst.de \
--to=hch@lst.de \
--cc=Conor.Dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=rppt@kernel.org \
--cc=sfr@canb.auug.org.au \
/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.