* Balbir Singh wrote:
> > Yes, turning off CONFIG_HSA_AMD_SVM fixes the issue, the strange memory
> > resource
> > afe-aff : :03:00.0
> > is gone.
> >
> > If one would add a max_pyhs_addr argument to devm_request_free_mem_region()
> > (which return the resource addr in kgd
* Linus Torvalds wrote:
> On Wed, 26 Mar 2025 at 15:00, Bert Karwatzki wrote:
> >
> > As Balbir Singh found out this memory comes from amdkfd
> > (kgd2kfd_init_zone_device()) with CONFIG_HSA_AMD_SVM=y. The memory gets
> > placed
> > by devm_request_free_mem_region() which places the memory at
* Balbir Singh wrote:
> > How frequently does this happen and what is the impact to users if
> > this happens?
>
> It happens a 100% of the time when the BAR space lies beyond the
> 10TiB region.
And how frequently is the BAR space beyond the 10TiB region, on modern
systems?
Thanks,
* Balbir Singh wrote:
> On 3/20/25 20:01, Ingo Molnar wrote:
> >
> > * Balbir Singh wrote:
> >
> >> On 3/17/25 00:09, Bert Karwatzki wrote:
> >>> This is related to the admgpu.gttsize. My laptop has the maximum amount
> >>> of memory (6
* Balbir Singh wrote:
> On 3/17/25 00:09, Bert Karwatzki wrote:
> > This is related to the admgpu.gttsize. My laptop has the maximum amount
> > of memory (64G) and usually gttsize is half of main memory size. I just
> > tested with cmdline="nokaslr amdgpi.gttsize=2048" and the problem does
>
