From: Matt Fleming <matt@codeblueprint.co.uk>
To: "Jonathan (Zhixiong) Zhang" <zjzhang@codeaurora.org>
Cc: Matt Fleming <matt.fleming@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, ying.huang@intel.com, fu.wei@linaro.org,
al.stone@linaro.org, bp@alien8.de, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 1/4] efi: x86: rearrange efi_mem_attributes()
Date: Mon, 15 Jun 2015 18:09:57 +0100 [thread overview]
Message-ID: <20150615170957.GC17685@codeblueprint.co.uk> (raw)
In-Reply-To: <1434157307-32318-2-git-send-email-zjzhang@codeaurora.org>
On Fri, 12 Jun, at 06:01:44PM, Jonathan (Zhixiong) Zhang wrote:
> From: "Jonathan (Zhixiong) Zhang" <zjzhang@codeaurora.org>
>
> x86 and ia64 implement efi_mem_attributes() differently. This
> function needs to be available for other arch (such as arm64)
> as well, such as for the purpose of ACPI/APEI.
>
> ia64 efi does not setup memmap variable and does not set
> EFI_MEMMAP flag, so it needs to have its unique implementation
> of efi_mem_attributes().
Something like the above paragraph...
> @@ -517,3 +517,21 @@ char * __init efi_md_typeattr_format(char *buf, size_t size,
> attr & EFI_MEMORY_UC ? "UC" : "");
> return buf;
> }
needs to go here, i.e. as documentation for efi_mem_atributes(). You
need to explain why this function is marked as __weak at the function
definition site.
> +u64 __weak efi_mem_attributes(unsigned long phys_addr)
> +{
> + efi_memory_desc_t *md;
> + void *p;
> +
> + if (!efi_enabled(EFI_MEMMAP))
> + return 0;
> +
> + for (p = memmap.map; p < memmap.map_end; p += memmap.desc_size) {
> + md = p;
> + if ((md->phys_addr <= phys_addr) &&
> + (phys_addr < (md->phys_addr +
> + (md->num_pages << EFI_PAGE_SHIFT))))
> + return md->attribute;
> + }
> + return 0;
> +}
because otherwise people are going to read this in the future and think,
"efi_mem_attribute() doesn't quite work how I want it to for my arch,
but it's __weak, so I'll override it"
which is absolutely not the practice we should be promoting.
How about something like this,
/*
* efi_mem_attributes - lookup memmap attributes for physical address
* @phys_addr: the physical address to lookup
*
* Search in the EFI memory map for the region covering
* @phys_addr. Returns the EFI memory attributes if the region
* was found in the memory map, 0 otherwise.
*
* Despite being marked __weak most architectures should *not*
* override this function. It is __weak solely for the benefit
* of ia64 which has a funky EFI memory map that doesn't work
* the same way as other architectures.
*/
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-06-15 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 1:01 [PATCH V4 0/4] map GHES memory region according to EFI memory map Jonathan (Zhixiong) Zhang
2015-06-13 1:01 ` [PATCH V4 1/4] efi: x86: rearrange efi_mem_attributes() Jonathan (Zhixiong) Zhang
2015-06-15 17:09 ` Matt Fleming [this message]
[not found] ` <20150615170957.GC17685-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-06-15 22:24 ` Zhang, Jonathan Zhixiong
2015-06-13 1:01 ` [PATCH V4 2/4] x86: acpi: add arch_apei_get_mem_attributes() Jonathan (Zhixiong) Zhang
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=20150615170957.GC17685@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=al.stone@linaro.org \
--cc=bp@alien8.de \
--cc=fu.wei@linaro.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
--cc=zjzhang@codeaurora.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).