From: David Daney <ddaney.cavm@gmail.com>
To: Sanjay Lal <sanjayl@kymasys.com>
Cc: linux-mips@linux-mips.org, kvm@vger.kernel.org,
ralf@linux-mips.org, gleb@redhat.com, mtosatti@redhat.com
Subject: Re: [PATCH] KVM/MIPS32: Export min_low_pfn.
Date: Fri, 17 May 2013 14:42:48 -0700 [thread overview]
Message-ID: <5196A458.7080400@gmail.com> (raw)
In-Reply-To: <1368824818-22503-1-git-send-email-sanjayl@kymasys.com>
On 05/17/2013 02:06 PM, Sanjay Lal wrote:
> The KVM module uses the standard MIPS cache management routines, which use min_low_pfn.
> This creates and indirect dependency, requiring min_low_pfn to be exported.
>
> Signed-off-by: Sanjay Lal <sanjayl@kymasys.com>
> ---
> arch/mips/kernel/mips_ksyms.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/mips/kernel/mips_ksyms.c b/arch/mips/kernel/mips_ksyms.c
> index 6e58e97..0299472 100644
> --- a/arch/mips/kernel/mips_ksyms.c
> +++ b/arch/mips/kernel/mips_ksyms.c
> @@ -14,6 +14,7 @@
> #include <linux/mm.h>
> #include <asm/uaccess.h>
> #include <asm/ftrace.h>
> +#include <linux/bootmem.h>
>
> extern void *__bzero(void *__s, size_t __count);
> extern long __strncpy_from_user_nocheck_asm(char *__to,
> @@ -60,3 +61,8 @@ EXPORT_SYMBOL(invalid_pte_table);
> /* _mcount is defined in arch/mips/kernel/mcount.S */
> EXPORT_SYMBOL(_mcount);
> #endif
> +
> +/* The KVM module uses the standard MIPS cache functions which use
> + * min_low_pfn, requiring it to be exported.
> + */
> +EXPORT_SYMBOL(min_low_pfn);
I think I asked this before, but I don't remember the answer:
Why not put EXPORT_SYMBOL(min_low_pfn) in mm/bootmem.c adjacent to where
the symbol is defined?
Cluttering up the kernel with multiple architectures all doing
architecture specific exports of the same symbol is not a clean way of
doing things.
The second time something needs to be done, it should be factored out
into common code.
David Daney
>
next prev parent reply other threads:[~2013-05-17 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 21:06 [PATCH] KVM/MIPS32: Export min_low_pfn Sanjay Lal
2013-05-17 21:42 ` David Daney [this message]
2013-05-18 6:36 ` Gleb Natapov
2013-05-19 9:22 ` Ralf Baechle
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=5196A458.7080400@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mtosatti@redhat.com \
--cc=ralf@linux-mips.org \
--cc=sanjayl@kymasys.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