All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Bharata B Rao <bharata@amd.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	luto@kernel.org, peterz@infradead.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com,
	nikunj@amd.com, Balbir Singh <balbirs@nvidia.com>,
	kees@kernel.org, alexander.deucher@amd.com
Subject: Re: AMD GPU driver load hitting BUG_ON in sync_global_pgds_l5()
Date: Wed, 23 Apr 2025 09:01:54 -0700	[thread overview]
Message-ID: <2cba2ae9-e29d-4eab-a77a-678be0b09a58@intel.com> (raw)
In-Reply-To: <83cf7fc7-23e0-46f5-916b-5341a0ab9599@amd.com>

On 4/23/25 02:30, Bharata B Rao wrote:
> On 22-Apr-25 8:43 PM, Dave Hansen wrote:
>> On 4/21/25 23:34, Bharata B Rao wrote:
>>> At the outset, it appears that the selection of vmemmap_base doesn't
>>> seem to consider if there is going to be enough room of accommodating
>>> future hot plugged pages.
>>
>> Is this future hotplug area in the memory map at boot?
> 
> The KVM guest isn't using any -m maxmem option if that's what you are
> hinting at.

How could vmemmap_base consider future hotplug areas if it isn't told
where they will be?


  reply	other threads:[~2025-04-23 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  6:34 AMD GPU driver load hitting BUG_ON in sync_global_pgds_l5() Bharata B Rao
2025-04-22  7:14 ` Balbir Singh
2025-04-22  8:28   ` Bharata B Rao
2025-04-23  6:40   ` Bharata B Rao
2025-04-22 15:13 ` Dave Hansen
2025-04-23  9:30   ` Bharata B Rao
2025-04-23 16:01     ` Dave Hansen [this message]
2025-04-24 12:54       ` Bharata B Rao

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=2cba2ae9-e29d-4eab-a77a-678be0b09a58@intel.com \
    --to=dave.hansen@intel.com \
    --cc=alexander.deucher@amd.com \
    --cc=balbirs@nvidia.com \
    --cc=bharata@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nikunj@amd.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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.