From: geoff@infradead.org (Geoff Levand)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64 spin-table cpu-return-addr
Date: Fri, 08 Aug 2014 17:30:00 -0700 [thread overview]
Message-ID: <1407544200.8971.138.camel@smoke> (raw)
Hi Mark,
Regarding adding a cpu-return-addr property to the spin-table
cpu enable method for arm64, we need to decide how to handle
a difference in endian mode between the kernel and the
spin-table code.
Will the spin-table code always be built as little endian? If
so, then either the kernel or the spin code could handle this
difference, and we need to decide which will do it. If not,
then the only way is for the spin code to do it as the kernel
has no way to tell endian mode of the spin code, unless to test
and save how it was entered at startup.
Let me know your thoughts.
-Geoff
next reply other threads:[~2014-08-09 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 0:30 Geoff Levand [this message]
2014-08-12 10:50 ` arm64 spin-table cpu-return-addr Mark Rutland
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=1407544200.8971.138.camel@smoke \
--to=geoff@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).