From: Scott Wood <scottwood@freescale.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Jeremy Kerr <jk@ozlabs.org>
Subject: Re: [PATCH 1/2] powerpc: Add a proper syscall for switching endianness
Date: Fri, 13 Mar 2015 14:50:50 -0500 [thread overview]
Message-ID: <1426276250.27998.6.camel@freescale.com> (raw)
In-Reply-To: <1426228726.23806.3.camel@ellerman.id.au>
On Fri, 2015-03-13 at 17:38 +1100, Michael Ellerman wrote:
> On Fri, 2015-03-13 at 15:39 +1100, Michael Ellerman wrote:
> > We currently have a "special" syscall for switching endianness. This is
> > syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall
> > exception entry.
> >
> > diff --git a/arch/powerpc/include/asm/systbl.h b/arch/powerpc/include/asm/systbl.h
> > index 91062eef582f..c3ee21a1d9cf 100644
> > --- a/arch/powerpc/include/asm/systbl.h
> > +++ b/arch/powerpc/include/asm/systbl.h
> > @@ -367,3 +367,4 @@ SYSCALL_SPU(getrandom)
> > SYSCALL_SPU(memfd_create)
> > SYSCALL_SPU(bpf)
> > COMPAT_SYS(execveat)
> > +PPC_SYS(switch_endian)
>
> And of course I forgot about 32-bit.
>
> According to Paul there are no working implementations of LE on 32-bit cpus, so
> the syscall doesn't really make sense there.
>
> Scott does that sound right to you for FSL stuff?
We don't support LE on FSL chips.
-Scott
next prev parent reply other threads:[~2015-03-13 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 4:39 [PATCH 1/2] powerpc: Add a proper syscall for switching endianness Michael Ellerman
2015-03-13 4:39 ` [PATCH 2/2] selftests/powerpc: Add a test of the switch_endian() syscall Michael Ellerman
2015-03-13 5:01 ` Michael Ellerman
2015-03-13 7:10 ` Ram Pai
2015-03-13 7:16 ` Michael Ellerman
2015-03-13 6:38 ` [PATCH 1/2] powerpc: Add a proper syscall for switching endianness Michael Ellerman
2015-03-13 19:50 ` Scott Wood [this message]
2015-03-15 22:59 ` Tony Breeds
2015-03-16 0:07 ` Benjamin Herrenschmidt
2015-03-16 3:10 ` Michael Ellerman
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=1426276250.27998.6.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).