From: Will Deacon <will@kernel.org>
To: Catalin M arinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org,
D Scott Phillips <scott@os.amperecomputing.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Alison Schofield <alison.schofield@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Ankit Agrawal <ankita@nvidia.com>, Baoquan He <bhe@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wang Jinchao <wangjinchao@xfusion.com>,
linux-kernel@vger.kernel.org, patches@amperecomputing.com
Subject: Re: [PATCH v3] arm64: Expose the end of the linear map in PHYSMEM_END
Date: Wed, 4 Sep 2024 17:12:36 +0100 [thread overview]
Message-ID: <172546436035.2663988.13656024915203929376.b4-ty@kernel.org> (raw)
In-Reply-To: <20240903164532.3874988-1-scott@os.amperecomputing.com>
On Tue, 03 Sep 2024 09:45:32 -0700, D Scott Phillips wrote:
> The memory hot-plug and resource management code needs to know the
> largest address which can fit in the linear map, so set
> PHYSMEM_END for that purpose.
>
> This fixes a crash[1] at boot when amdgpu tries to create
> DEVICE_PRIVATE_MEMORY and is given a physical address by the
> resource management code which is outside the range which can have
> a `struct page`
>
> [...]
Applied to arm64 (for-next/mm), thanks!
I dropped the cc: stable, however, as PHYSMEM_END looks like it only
exists in linux-next.
[1/1] arm64: Expose the end of the linear map in PHYSMEM_END
https://git.kernel.org/arm64/c/eeb8fdfcf090
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2024-09-04 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 16:45 D Scott Phillips
2024-09-03 17:03 ` Andy Shevchenko
2024-09-04 16:12 ` Will Deacon [this message]
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=172546436035.2663988.13656024915203929376.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andreyknvl@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ankita@nvidia.com \
--cc=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patches@amperecomputing.com \
--cc=scott@os.amperecomputing.com \
--cc=takahiro.akashi@linaro.org \
--cc=wangjinchao@xfusion.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®