From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v5 0/2] ARM: VFP: Save / restore VFP state on the signal handler path
Date: Mon, 12 Apr 2010 23:04:40 +0100 [thread overview]
Message-ID: <20100412220440.GF6148@shareable.org> (raw)
In-Reply-To: <cover.1270199787.git.imre.deak@nokia.com>
imre.deak at nokia.com wrote:
> From: Imre Deak <imre.deak@nokia.com>
>
> Changes since v4:
> - Do not add the packed attribute to user_vfp or user_vfp_exc.
> I added packed to these structs to prevent the extra padding in
> vfp_sigframe. But actually the padding is in accordance with the
> ARM ABI.
EABI, OABI or both?
In general it's a really good idea, if you know there will be padding,
to insert dummy fields where the padding goes so that it doesn't make
any difference what compiler, ABI and settings are used.
-- Jamie
next prev parent reply other threads:[~2010-04-12 22:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1242744292-23776-1-git-send-email-imre.deak@nokia.com>
2010-02-04 21:37 ` [RFC PATCH v2 0/2] ARM: VFP: Save / restore VFP state on the signal handler path Imre Deak
2010-02-04 21:38 ` [RFC PATCH v2 1/2] ARM: VFP: add support to sync the VFP state of the current thread Imre Deak
2010-02-06 10:32 ` Russell King - ARM Linux
2010-02-06 11:20 ` Russell King - ARM Linux
2010-02-06 11:32 ` Russell King - ARM Linux
2010-02-06 11:41 ` Russell King - ARM Linux
2010-02-06 15:55 ` Imre Deak
2010-02-04 21:38 ` [RFC PATCH v2 2/2] ARM: VFP: preserve the HW context when calling signal handlers Imre Deak
2010-02-06 9:25 ` Russell King - ARM Linux
2010-02-06 10:02 ` Imre Deak
2010-02-06 12:12 ` Russell King - ARM Linux
2010-02-06 16:23 ` Imre Deak
2010-03-29 16:17 ` [RFC PATCH v3 0/3] ARM: VFP: Save / restore VFP state on the signal handler path imre.deak at nokia.com
2010-03-31 21:23 ` [RFC PATCH v4 " imre.deak at nokia.com
2010-04-02 14:36 ` [RFC PATCH v5 0/2] " imre.deak at nokia.com
2010-04-02 14:36 ` [RFC PATCH v5 1/2] ARM: VFP: fix the SMP versions of vfp_{sync, flush}_hwstate imre.deak at nokia.com
2010-04-12 18:39 ` [RFC PATCH v5 1/2] ARM: VFP: fix the SMP versions of vfp_{sync,flush}_hwstate Russell King - ARM Linux
2010-04-02 14:36 ` [RFC PATCH v5 2/2] ARM: VFP: preserve the HW context when calling signal handlers imre.deak at nokia.com
2010-04-12 18:41 ` Russell King - ARM Linux
2010-04-12 22:04 ` Jamie Lokier [this message]
2010-04-13 11:42 ` [RFC PATCH v5 0/2] ARM: VFP: Save / restore VFP state on the signal handler path Imre Deak
2010-04-13 11:59 ` Nicolas Pitre
2010-04-07 16:24 ` [RFC PATCH v4 0/3] " Dirk Behme
2010-04-07 16:39 ` Imre Deak
2010-04-07 17:31 ` Jason McMullan
2010-03-31 21:23 ` [RFC PATCH v4 1/3] ARM: VFP: fix the SMP versions of vfp_{sync, flush}_hwstate imre.deak at nokia.com
2010-03-31 21:23 ` [RFC PATCH v4 2/3] ARM: VFP: make user_vfp struct packed imre.deak at nokia.com
2010-03-31 21:23 ` [RFC PATCH v4 3/3] ARM: VFP: preserve the HW context when calling signal handlers imre.deak at nokia.com
2010-03-29 16:17 ` [RFC PATCH v3 1/3] ARM: VFP: add support to sync the VFP state of the current thread imre.deak at nokia.com
2010-03-29 16:17 ` [RFC PATCH v3 2/3] ARM: VFP: make user_vfp struct packed imre.deak at nokia.com
2010-03-29 16:17 ` [RFC PATCH v3 3/3] ARM: VFP: preserve the HW context when calling signal handlers imre.deak at nokia.com
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=20100412220440.GF6148@shareable.org \
--to=jamie@shareable.org \
--cc=linux-arm-kernel@lists.infradead.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.