From: Borislav Petkov <bp@alien8.de>
To: Kairui Song <kasong@redhat.com>
Cc: Thomas Lendacky <Thomas.Lendacky@amd.com>,
Lianbo Jiang <lijiang@redhat.com>, Baoquan He <bhe@redhat.com>,
x86@kernel.org,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH v2] x86/kdump: Reserve extra memory when SME or SEV is active
Date: Thu, 5 Sep 2019 18:29:09 +0200 [thread overview]
Message-ID: <20190905162909.GF19246@zn.tnic> (raw)
In-Reply-To: <e70f1e99-f696-51e2-f50c-148bcda5dfb6@redhat.com>
On Mon, Sep 02, 2019 at 03:38:22PM +0800, Kairui Song wrote:
> Will it be good if the final code looks like this?
>
> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> index 48115cf11e0f..754b25d6e785 100644
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@ -526,6 +526,69 @@ static int __init reserve_crashkernel_low(void)
> return 0;
> }
> +static int __init crashkernel_find_region(
> + unsigned long long *base,
> + unsigned long long *size,
> + bool high)
Those should be aligned at the opening brace.
> +{
> + unsigned long long start, mem_enc_req = 0;
Declare that mem_enc_req in the if (!high) branch below, where you need it only.
> +
> + /*
> + * *base == 0 means: find the address automatically, else just
> + * verify the region is useable
> + */
> + if (*base) {
> + start = memblock_find_in_range(*base, *base + *size,
> + *size, 1 << 20);
> + if (start != *base) {
> + pr_info("crashkernel reservation failed - memory is in use.\n");
> + return -EBUSY;
I don't like functions which change external variables passed as
pointers but then in the error case, change those unnecessarily. Write
into *base and *size only in the success case pls and use local vars for
the intermediate results.
Also, those retvals are not visible to userspace - just return negative for
error and 0 for success.
> + }
> + return 0;
> + }
> +
> + /*
> + * Set CRASH_ADDR_LOW_MAX upper bound for crash memory,
> + * crashkernel=x,high reserves memory over 4G, also allocates
> + * 256M extra low memory for DMA buffers and swiotlb.
> + * But the extra memory is not required for all machines.
> + * So try low memory first and fall back to high memory
> + * unless "crashkernel=size[KMG],high" is specified.
> + */
> + if (!high) {
if (high)
goto high_reserve;
< now save an indentation level >
> + /*
> + * When SME/SEV is active and not using high reserve,
> + * it will always required an extra SWIOTLB region.
> + */
> + if (mem_encrypt_active())
> + mem_enc_req = ALIGN(swiotlb_size_or_default(), SZ_1M);
> +
> + *base = memblock_find_in_range(CRASH_ALIGN,
> + CRASH_ADDR_LOW_MAX,
> + *size + mem_enc_req,
> + CRASH_ALIGN);
> + if (*base) {
> + if (mem_enc_req) {
> + pr_info("Memory encryption is active, crashkernel needs %ldMB extra memory\n",
> + (unsigned long)(mem_enc_req >> 20));
> + *size += mem_enc_req;
> + }
> + return 0;
> + }
> + }
> +
high_reserve:
> + /* Try high reserve */
> + *base = memblock_find_in_range(CRASH_ALIGN,
> + CRASH_ADDR_HIGH_MAX,
> + *size, CRASH_ALIGN);
> + if (!*base) {
> + pr_info("crashkernel reservation failed - No suitable area found.\n");
> + return -ENOMEM;
> + }
> +
> + return 0;
> +}
...
> If you are OK with this, I will split it into two patch and send V3.
With that, yes, this looks a bit better.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2019-09-05 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190826044535.9646-1-kasong@redhat.com>
2019-08-26 23:53 ` [PATCH v2] x86/kdump: Reserve extra memory when SME or SEV is active Kairui Song
2019-08-27 5:46 ` Baoquan He
2019-08-27 13:43 ` Lendacky, Thomas
2019-08-30 16:45 ` Borislav Petkov
2019-09-02 7:38 ` Kairui Song
2019-09-05 16:29 ` Borislav Petkov [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=20190905162909.GF19246@zn.tnic \
--to=bp@alien8.de \
--cc=Thomas.Lendacky@amd.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=kasong@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox