From: David Hildenbrand <david@redhat.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
will@kernel.org, catalin.marinas@arm.com,
linux-kernel@vger.kernel.org, Steven Price <steven.price@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] arm64/mm: Validate hotplug range before creating linear mapping
Date: Mon, 19 Oct 2020 16:58:49 +0200 [thread overview]
Message-ID: <34ab00af-ebdc-6b83-4ff6-1e7bb9f7c3a3@redhat.com> (raw)
In-Reply-To: <40104165-aa6f-201c-4aa2-e3918978dc6e@arm.com>
>>
>> Most probably,
>>
>> struct range memhp_get_addressable_range(bool need_mapping)
>> {
>> ...
>> }
>
> Something like this...
>
> +struct memhp_range {
> + u64 start;
> + u64 end;
> +};
We do have struct range already in include/linux/range.h
> +
> +#ifndef arch_get_addressable_range
> +static inline struct memhp_range arch_get_mappable_range(bool need_mapping)
> +{
> + struct memhp_range range = {
> + .start = 0UL,
> + .end = (1ull << (MAX_PHYSMEM_BITS + 1)) - 1,
Or just set to -1ULL if it's only used in memhp_get_mappable_range(), to
keep things simple ().
> + };
> + return range;
> +}
> +#endif
> +
> +static inline struct memhp_range memhp_get_mappable_range(bool need_mapping)
due to "need_mapping" the function might better be called
memhp_get_pluggable_range()
or similar
> +{
> + const u64 max_phys = (1ull << (MAX_PHYSMEM_BITS + 1)) - 1;
> + struct memhp_range range = arch_get_mappable_range(need_mapping);
> +
> + if (range.start > max_phys) {
> + range.start = 0;
> + range.end = 0;
> + }
> + range.end = min_t(u64, range.end, max_phys);
> + return range;
> +}
> +
> +static inline bool memhp_range_allowed(u64 start, u64 end, bool need_mapping)
> +{
> + struct memhp_range range = memhp_get_mappable_range(need_mapping);
> +
> + return (start <= end) && (start >= range.start) && (end <= range.end);
Keep in mind that in memory hotplug code, "end" is usually exclusive,
and "end" in "struct range" is inclusive (see range_len(), or how you
calculate max_phys.
So depending on the semantics, you might have to fixup your comparisons.
return start < end && start >= range.start && end <= range.end - 1;
[...]
>> Right now it's like calling a function with wrong arguments - you just
>> don't have a clue what valid arguments are, because non-obvious errors
>> (besides -ENOMEM, which is a temporary error) pop up deep down the call
>> chain.
>>
>> For example, virito-mem would use it to detect during device
>> initialization the usable device range, and warn the user accordingly.
>> It currently manually checks for MAX_PHYSMEM_BITS, but that's just ugly.
>> Failing at random add_memory() calls (permanently!) is not so nice.
>>
>> In case of DIMMs, we could use it to detect if adding parts of a DIMM
>> won't work (and warn the user early). We could try to add as much as
>> possible.
>
> Agreed.
>
> Planning to add memhp_range_allowed() check in add_memory(), __add_memory(),
> add_memory_driver_managed() and memremap_pages(). This check might just get
> called twice depending on the hotplug path. Wondering if this needs to be
> added any where else ?
So
add_memory() needs to
- add sections via arch_add_memory()
- create a mapping via arch_add_memory()->add_pages()
memremap_pages() via arch_add_memory() needs to
- add sections via arch_add_memory()
- create a mapping via arch_add_memory()->add_pages()
memremap_pages() via add_pages() needs to
- add sections
I'll reuse the functions from virtio-mem code once in place (exposing
memhp_get_pluggable_range()).
I do agree that having the callers of arch_add_memory() / add_pages()
validate stuff isn't completely nice. I already raised that I would much
rather want to see !arch wrappers for these arch functions that could
validate stuff. But then we would have to do a bigger cleanup to get
naming right.
1. Rename functions for handling system ram like
s/add_memory/add_sysram/
s/remove_memory/remove_sysram/
...
2. Have a new add_memory() that validates + calls arch_add_memory()
3. s/add_pages/arch_add_pages/
4. Have a new add_pages() that validates + calls arch_add_pages()
...
Long story short, handling it in the 2 (!) callers might be easier for now.
--
Thanks,
David / dhildenb
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-10-19 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 8:46 [PATCH] arm64/mm: Validate hotplug range before creating linear mapping Anshuman Khandual
2020-09-28 20:35 ` Will Deacon
2020-09-29 8:04 ` Anshuman Khandual
2020-09-29 15:22 ` Will Deacon
2020-09-30 8:02 ` Anshuman Khandual
2020-09-30 11:01 ` Ard Biesheuvel
2020-10-06 6:28 ` Anshuman Khandual
2020-10-06 6:35 ` Anshuman Khandual
2020-10-12 7:29 ` Ard Biesheuvel
2020-10-14 5:06 ` Anshuman Khandual
2020-10-14 6:37 ` Ard Biesheuvel
2020-10-06 15:34 ` David Hildenbrand
2020-10-07 2:50 ` Anshuman Khandual
2020-10-07 8:39 ` David Hildenbrand
2020-10-19 11:23 ` Anshuman Khandual
2020-10-19 14:58 ` David Hildenbrand [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=34ab00af-ebdc-6b83-4ff6-1e7bb9f7c3a3@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@kernel.org \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).