[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <158827870560.24445.10969636442610279958.b4-ty@kernel.org>
Date: Thu, 30 Apr 2020 22:12:25 +0100
From: Will Deacon <will@...nel.org>
To: linux-kernel@...r.kernel.org, Will Deacon <will.deacon@....com>,
Catalin Marinas <catalin.marinas@....com>,
linux-arm-kernel@...ts.infradead.org,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Mark Rutland <mark.rutland@....com>, x86@...nel.org,
Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>,
Łukasz Stelmach <l.stelmach@...sung.com>
Cc: Will Deacon <will@...nel.org>, Vivek Goyal <vgoyal@...hat.com>,
Bhupesh Sharma <bhsharma@...hat.com>,
AKASHI Takahiro <takahiro.akashi@...aro.org>,
James Morse <james.morse@....com>,
Thiago Jung Bauermann <bauerman@...ux.vnet.ibm.com>
Subject: Re: [PATCH v2 0/2] Make memory size reporting in kexec_file_load() accurate
On Thu, 30 Apr 2020 18:31:40 +0200, =?UTF-8?q?=C5=81ukasz=20Stelmach?= wrote:
> Calling kexec_add_buffer() page-alligns the value of kbuf.memsz, so it
> is not same as the requested value. Hence both bufsz and memsz should
> after kexec_add_buffer() is called should be be reported separately.
>
> Łukasz Stelmach (2):
> arm64: kexec_file: print appropriate variable
> x86: kexec_file: print appropriate variable
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/2] arm64: kexec_file: print appropriate variable
https://git.kernel.org/arm64/c/51075e0cb759
[2/2] x86: kexec_file: print appropriate variable
(not applied)
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
Powered by blists - more mailing lists