All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] arm: fix u-boot port syscall interface va_arg handling (was Re: [PATCH] [ARM] Enable boot module for arm)
Date: Sat, 16 Nov 2013 15:03:16 +0100	[thread overview]
Message-ID: <52877B24.2040002@gmail.com> (raw)
In-Reply-To: <20131116135340.GE30374@rocoto.smurfnet.nu>

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

On 16.11.2013 14:53, Leif Lindholm wrote:
> On Sat, Nov 16, 2013 at 02:17:51PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>> From an ABI perspective, grub_uboot_syscall is a veneer:
>>> the only visible side effect it is permitted to have is to corrupt r12.
>>>
>> According to wikipedia:
>> "Subroutines must preserve the contents of r4 to r11 and the stack pointer."
>> So changing r9 sounds to me like this is actually U-Boot bug and
>> preserving it sounds like right way to handle it.
> 
> No. grub_uboot_syscall is not a subroutine - it is a veneer.
> We have a specific reason to need to preserve r8, over and above what
> the ABI says, because u-boot has hijacked it.
> 
> But now I went to look at the u-boot code, and suddenly I want to cry.
> Commit fe1378a961e508b31b1f29a2bb08ba1dac063155 changes the register
> reserved for global data from r8 to r9. Which means we need to preserve
> both since they didn't step the API version number.
> 
> *sigh*
> 
> Updated patch attached.

Go ahead.
> 
> /
>     Leif
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

  reply	other threads:[~2013-11-16 14:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-21 13:20 [PATCH] [ARM] Enable boot module for arm Francesco Lavra
2013-07-25 14:36 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-07-25 14:45   ` Francesco Lavra
2013-07-25 15:04     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-07-27  3:46       ` Andrey Borzenkov
2013-07-27  4:21         ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-07-27  5:19           ` Andrey Borzenkov
2013-07-27 14:44             ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-07-28 16:51               ` Andrey Borzenkov
2013-07-28 18:01                 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-07-28 18:18                   ` Andrey Borzenkov
2013-07-28 19:01                     ` Andrey Borzenkov
2013-11-15 19:13           ` Andrey Borzenkov
2013-11-16  0:45             ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-16 12:39               ` Leif Lindholm
2013-11-16 12:49                 ` [PATCH] arm: fix u-boot port syscall interface va_arg handling (was Re: [PATCH] [ARM] Enable boot module for arm) Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-16 13:00                   ` Leif Lindholm
2013-11-16 13:17                     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-16 13:27                       ` Andrey Borzenkov
2013-11-16 13:53                       ` Leif Lindholm
2013-11-16 14:03                         ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-11-16 14:28                           ` Leif Lindholm
2013-11-16 14:45                             ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-16 14:45                             ` Leif Lindholm
2013-11-16 15:19                               ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-16 15:23                                 ` Leif Lindholm
2013-11-16 15:31                                   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-16 12:54               ` [PATCH] [ARM] Enable boot module for arm Andrey Borzenkov

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=52877B24.2040002@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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.