From: Mark Rutland <mark.rutland@arm•com>
To: Julien Grall <julien.grall@arm•com>
Cc: Stefano Stabellini <sstabellini@kernel•org>,
Arnd Bergmann <arnd@arndb•de>,
Andrew Cooper <andrew.cooper3@citrix•com>,
Emil Velikov <emil.l.velikov@gmail•com>,
Russell King <linux@armlinux•org.uk>,
Denis Efremov <efremov@linux•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext•com>,
xen-devel <xen-devel@lists•xenproject.org>,
Will Deacon <will@kernel•org>,
Linux ARM <linux-arm-kernel@lists•infradead.org>
Subject: Re: [Xen-devel] [PATCH] ARM: xen: unexport HYPERVISOR_platform_op function
Date: Tue, 1 Oct 2019 15:33:43 +0100 [thread overview]
Message-ID: <20191001143334.GA46651@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <95dbd972-fe78-d0ca-f7b4-1a6bdd418eab@arm.com>
Hi Julien,
On Sat, Sep 07, 2019 at 11:05:45AM +0100, Julien Grall wrote:
> On 9/6/19 6:20 PM, Andrew Cooper wrote:
> > On 06/09/2019 17:00, Arnd Bergmann wrote:
> > > On Fri, Sep 6, 2019 at 5:55 PM Andrew Cooper <andrew.cooper3@citrix•com> wrote:
> > > > On 06/09/2019 16:39, Arnd Bergmann wrote:
> > > > > HYPERVISOR_platform_op() is an inline function and should not
> > > > > be exported. Since commit 15bfc2348d54 ("modpost: check for
> > > > > static EXPORT_SYMBOL* functions"), this causes a warning:
> > > > >
> > > > > WARNING: "HYPERVISOR_platform_op" [vmlinux] is a static EXPORT_SYMBOL_GPL
> > > > >
> > > > > Remove the extraneous export.
> > > > >
> > > > > Fixes: 15bfc2348d54 ("modpost: check for static EXPORT_SYMBOL* functions")
> > > > > Signed-off-by: Arnd Bergmann <arnd@arndb•de>
> > > > Something is wonky. That symbol is (/ really ought to be) in the
> > > > hypercall page and most definitely not inline.
> > > >
> > > > Which tree is that changeset from? I can't find the SHA.
> > > This is from linux-next, I think from the kbuild tree.
> >
> > Thanks.
> >
> > Julien/Stefano: Why are any of these hypercalls out-of-line? ARM
> > doesn't use the hypercall page, and there is no argument translation
> > (not even in arm32 as there are no 5-argument hypercalls declared).
>
> I am not sure how the hypercall page makes things different. You still have
> to store the arguments in the correct register so...
>
> >
> > They'd surely be easier to implement with a few static inlines and some
> > common code, than to try and replicate the x86 side hypercall_page
> > interface ?
>
> ... I don't think they will be easier to implement with a few static
> inlines. The implementation will likely end up to be similar to
> arch/x86/asm/xen/hypercall.h.
>
> Furthermore, one of the downside of per-arch static inline is it is more
> difficult to ensure the prototype match for all the architectures. Although,
> it might be possible to make them common by only requesting per-arch to
> implement HYPERCALL_N(...).
>
> So I think the code is better as it is.
>
> While looking at the code, I also realized that the implementation of
> HYPERCALL_dm_op might be incorrect for Arm32. Similarly do privcmd call, I
> think dm_op call should enable user access as they will be used by
> userspace.
>
> We don't use dm_op on Arm so far, hence why I think this was unnoticed. I
> will see if I can reproduce it and send a patch.
I'm seeing this when building arm64 defconfig v5.4-rc1:
| [mark@lakrids:~/src/linux]% usekorg 8.1.0 make ARCH=arm64 CROSS_COMPILE=aarch64-linux- -j56 -s
| arch/arm64/Makefile:62: CROSS_COMPILE_COMPAT not defined or empty, the compat vDSO will not be built
| WARNING: "HYPERVISOR_platform_op" [vmlinux] is a static EXPORT_SYMBOL_GPL
| WARNING: "HYPERVISOR_platform_op" [vmlinux] is a static EXPORT_SYMBOL_GPL
I couldn't see a follow-up; do you have a patch for this?
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-01 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 15:39 [PATCH] ARM: xen: unexport HYPERVISOR_platform_op function Arnd Bergmann
2019-09-06 15:55 ` [Xen-devel] " Andrew Cooper
2019-09-06 15:59 ` Jan Beulich
2019-09-06 16:00 ` Arnd Bergmann
2019-09-06 17:20 ` Andrew Cooper
2019-09-07 10:05 ` Julien Grall
2019-10-01 14:33 ` Mark Rutland [this message]
2019-10-01 14:39 ` Julien Grall
2019-10-01 14:46 ` Mark Rutland
2019-10-01 17:38 ` Stefano Stabellini
2019-10-01 18:57 ` Arnd Bergmann
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=20191001143334.GA46651@lakrids.cambridge.arm.com \
--to=mark.rutland@arm$(echo .)com \
--cc=andrew.cooper3@citrix$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=efremov@linux$(echo .)com \
--cc=emil.l.velikov@gmail$(echo .)com \
--cc=julien.grall@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=sstabellini@kernel$(echo .)org \
--cc=will@kernel$(echo .)org \
--cc=xen-devel@lists$(echo .)xenproject.org \
--cc=yamada.masahiro@socionext$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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