All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
	stefano.stabellini@citrix.com, ian.campbell@citrix.com
Subject: Re: [PATCH v2 for 4.5] arm32: fix build after 063188f4b3
Date: Tue, 14 Oct 2014 17:31:23 +0100	[thread overview]
Message-ID: <543D4FDB.2080003@linaro.org> (raw)
In-Reply-To: <543D6B84020000780003ED55@mail.emea.novell.com>

On 10/14/2014 05:29 PM, Jan Beulich wrote:
>>>> On 14.10.14 at 17:52, <julien.grall@linaro.org> 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.
>>
>> Signed-off-by: Julien Grall <julien.grall@linaro.org>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>
>> ---
>> This is a fix for Xen 4.5 to compile the hypervisor with GCC 4.9.1, used by
>> Fedora & co.
>>
>> Jan: I kept your Signed-off-by for the commit message.
>>
>> Changes in v2:
>>     - Write the SMC call in assembly
>>     - Consolidate the code in a single place
> 
> To me it very much looks like (not just because of the subject) you
> sent v2 again, rather than v3.

Oh right. I will send the v3 in a couple of minutes.

Regards,



-- 
Julien Grall

  reply	other threads:[~2014-10-14 16:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 15:52 [PATCH v2 for 4.5] arm32: fix build after 063188f4b3 Julien Grall
2014-10-14 16:29 ` Jan Beulich
2014-10-14 16:31   ` Julien Grall [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-13 15:29 Julien Grall
2014-10-13 15:39 ` Julien Grall
2014-10-13 15:49 ` Jan Beulich
2014-10-13 16:05   ` Julien Grall
2014-10-13 15:51 ` Jan Beulich
2014-10-13 16:05   ` Julien Grall
2014-10-13 16:06 ` Stefano Stabellini
2014-10-13 16:49   ` Julien Grall
2014-10-13 17:01     ` Stefano Stabellini
2014-10-13 17:05       ` Julien Grall
2014-10-14  9:15 ` Ian Campbell
2014-10-14 12:43   ` Julien Grall
2014-10-14 12:57     ` Ian Campbell
2014-10-14 13:06       ` Julien Grall
2014-10-14 13:13         ` Jan Beulich
2014-10-14 13:18           ` Ian Campbell
2014-10-14 19:09           ` Tim Deegan
2014-10-15  7:31             ` 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=543D4FDB.2080003@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --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.