All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: Yury Norov <ynorov@caviumnetworks.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andrew Pinski <Andrew.Pinski@cavium.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"David S . Miller" <davem@davemloft.net>,
	Geethasowjanya Akula <Geethasowjanya.Akula@cavium.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ingo Molnar <mingo@kernel.org>, Kees Cook <keescook@chromium.org>,
	Laura Abbott <labbott@redhat.com>,
	Nicholas Piggin <npiggin@gmail.com>,
	Sunil Goutham <Sunil.Goutham@cavium.com>,
	Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH RFC 0/3] API for 128-bit IO access
Date: Wed, 24 Jan 2018 11:38:42 -0500	[thread overview]
Message-ID: <CAH8yC8nvD-CWt9eZ_CumwtVB0xAKKD1uosftAKGvxrhJhcneNw@mail.gmail.com> (raw)
In-Reply-To: <20180124090519.6680-1-ynorov@caviumnetworks.com>

On Wed, Jan 24, 2018 at 4:05 AM, Yury Norov <ynorov@caviumnetworks.com> wrote:
>
> ...
> With all that, this example code:
>
> static int __init 128bit_test(void)
> {
>         __uint128_t v;
>         __uint128_t addr;
>         __uint128_t val = (__uint128_t) 0x1234567890abc;
> ...

In case it matters, you can check for GCC support of the 128-bit types
in userland with:

#if (__SIZEOF_INT128__ >= 16)
   ...
#endif

Also see https://gcc.gnu.org/ml/gcc-help/2015-08/msg00185.html .

Jeff

WARNING: multiple messages have this Message-ID (diff)
From: noloader@gmail.com (Jeffrey Walton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/3] API for 128-bit IO access
Date: Wed, 24 Jan 2018 11:38:42 -0500	[thread overview]
Message-ID: <CAH8yC8nvD-CWt9eZ_CumwtVB0xAKKD1uosftAKGvxrhJhcneNw@mail.gmail.com> (raw)
In-Reply-To: <20180124090519.6680-1-ynorov@caviumnetworks.com>

On Wed, Jan 24, 2018 at 4:05 AM, Yury Norov <ynorov@caviumnetworks.com> wrote:
>
> ...
> With all that, this example code:
>
> static int __init 128bit_test(void)
> {
>         __uint128_t v;
>         __uint128_t addr;
>         __uint128_t val = (__uint128_t) 0x1234567890abc;
> ...

In case it matters, you can check for GCC support of the 128-bit types
in userland with:

#if (__SIZEOF_INT128__ >= 16)
   ...
#endif

Also see https://gcc.gnu.org/ml/gcc-help/2015-08/msg00185.html .

Jeff

  parent reply	other threads:[~2018-01-24 16:38 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24  9:05 [PATCH RFC 0/3] API for 128-bit IO access Yury Norov
2018-01-24  9:05 ` Yury Norov
2018-01-24  9:05 ` Yury Norov
2018-01-24  9:05 ` [PATCH 1/3] UAPI: Introduce 128-bit types and byteswap operations Yury Norov
2018-01-24  9:05   ` Yury Norov
2018-01-24  9:05 ` [PATCH 2/3] asm-generic/io.h: API for 128-bit memory accessors Yury Norov
2018-01-24  9:05   ` Yury Norov
2018-01-24  9:05   ` Yury Norov
2018-01-24  9:05 ` [PATCH 3/3] arm64: enable 128-bit memory read/write support Yury Norov
2018-01-24  9:05   ` Yury Norov
2018-01-24 13:00   ` Geert Uytterhoeven
2018-01-24 13:00     ` Geert Uytterhoeven
2018-01-24 18:19     ` Yury Norov
2018-01-24 18:19       ` Yury Norov
2018-01-24 10:22 ` [PATCH RFC 0/3] API for 128-bit IO access Will Deacon
2018-01-24 10:22   ` Will Deacon
2018-01-26  9:05   ` Yury Norov
2018-01-26  9:05     ` Yury Norov
2018-01-26 18:11     ` Will Deacon
2018-01-26 18:11       ` Will Deacon
2018-01-29 10:25       ` Yury Norov
2018-01-29 10:25         ` Yury Norov
2018-01-24 10:28 ` Arnd Bergmann
2018-01-24 10:28   ` Arnd Bergmann
2018-01-24 15:48   ` Andy Shevchenko
2018-01-24 15:48     ` Andy Shevchenko
2018-01-24 15:48     ` Andy Shevchenko
2018-01-24 15:48     ` Andy Shevchenko
2018-01-25 11:38   ` Yury Norov
2018-01-25 11:38     ` Yury Norov
2018-01-25 11:38     ` Yury Norov
2018-01-25 12:11     ` Robin Murphy
2018-01-25 12:11       ` Robin Murphy
2018-01-25 12:11       ` Robin Murphy
2018-01-25 13:59     ` Arnd Bergmann
2018-01-25 13:59       ` Arnd Bergmann
2018-01-25 13:59       ` Arnd Bergmann
2018-01-24 16:38 ` Jeffrey Walton [this message]
2018-01-24 16:38   ` Jeffrey Walton

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=CAH8yC8nvD-CWt9eZ_CumwtVB0xAKKD1uosftAKGvxrhJhcneNw@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=Andrew.Pinski@cavium.com \
    --cc=Geethasowjanya.Akula@cavium.com \
    --cc=Sunil.Goutham@cavium.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=labbott@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=will.deacon@arm.com \
    --cc=ynorov@caviumnetworks.com \
    /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.