From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
Jan Beulich <jbeulich@suse.com>,
stefano.stabellini@citrix.com
Subject: Re: [PATCH v5 for 4.5] arm32: fix build after 063188f4b3
Date: Mon, 20 Oct 2014 11:49:40 +0100 [thread overview]
Message-ID: <1413802180.11781.6.camel@citrix.com> (raw)
In-Reply-To: <1413462858-17951-1-git-send-email-julien.grall@linaro.org>
On Thu, 2014-10-16 at 13:34 +0100, Julien Grall wrote:
> "xen: arm: Add support for the Exynos secure firmware" introduced code
> assuming that exynos_smc() would get called with arguments in certain
> registers. While the "noinline" attribute guarantees the function to
> not get inlined, it does not guarantee that all arguments arrive in the
> assumed registers: gcc's interprocedural analysis can result in clone
> functions to be created where some of the incoming arguments (commonly
> when they have constant values) get replaced by putting in place the
> respective values inside the clone.
>
> Xen contains in multiple place of this SMC function: consolidate the function
> in a single place and write it in assembly.
>
> Reported-by: Jan Beulich <jbeulich@suse.com>
> Signed-off-by: Julien Grall <julien.grall@linaro.org>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
I think a better $subject would be "xen: arm: introduce assembly helper
to call smc" and to begin the body with:
Commit 063188f4b3 "xen: arm: Add support for..."
If that's OK with you I'll make that change as I commit.
Ian.
next prev parent reply other threads:[~2014-10-20 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 12:34 [PATCH v5 for 4.5] arm32: fix build after 063188f4b3 Julien Grall
2014-10-20 10:49 ` Ian Campbell [this message]
2014-10-20 10:52 ` Julien Grall
2014-10-20 13:19 ` Ian Campbell
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=1413802180.11781.6.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.