From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: Expose support for optional ARMv8-A features
Date: Wed, 11 Oct 2017 13:37:05 +0100 [thread overview]
Message-ID: <20171011123705.GE11106@arm.com> (raw)
In-Reply-To: <20171010143530.fiomo7pqvtojflnn@localhost>
On Tue, Oct 10, 2017 at 03:35:30PM +0100, Catalin Marinas wrote:
> On Tue, Oct 10, 2017 at 10:53:10AM +0100, Suzuki K. Poulose wrote:
> > diff --git a/arch/arm64/include/uapi/asm/hwcap.h b/arch/arm64/include/uapi/asm/hwcap.h
> > index 4b9344cba83a..a4bad90a3fa3 100644
> > --- a/arch/arm64/include/uapi/asm/hwcap.h
> > +++ b/arch/arm64/include/uapi/asm/hwcap.h
> > @@ -36,5 +36,10 @@
> > #define HWCAP_FCMA (1 << 14)
> > #define HWCAP_LRCPC (1 << 15)
> > #define HWCAP_DCPOP (1 << 16)
> > +#define HWCAP_SHA3 (1 << 17)
> > +#define HWCAP_SM3 (1 << 18)
> > +#define HWCAP_SM4 (1 << 19)
> > +#define HWCAP_ASIMDDP (1 << 20)
> > +#define HWCAP_SHA512 (1 << 21)
>
> We may be getting some conflicts around these with additional patches
> coming in but not hard to solve. Anyway, whether we are getting pointer
> authentication in or not (probably the latter), I would really like to
> get the first patch in that series merged:
>
> http://lkml.kernel.org/r/1500480092-28480-2-git-send-email-mark.rutland at arm.com
Suzuki -- can you take Mark's patch above and update the documentation to
include the new hwcaps you've added, please?
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, Dave Martin <dave.martin@arm.com>
Subject: Re: [PATCH v2] arm64: Expose support for optional ARMv8-A features
Date: Wed, 11 Oct 2017 13:37:05 +0100 [thread overview]
Message-ID: <20171011123705.GE11106@arm.com> (raw)
In-Reply-To: <20171010143530.fiomo7pqvtojflnn@localhost>
On Tue, Oct 10, 2017 at 03:35:30PM +0100, Catalin Marinas wrote:
> On Tue, Oct 10, 2017 at 10:53:10AM +0100, Suzuki K. Poulose wrote:
> > diff --git a/arch/arm64/include/uapi/asm/hwcap.h b/arch/arm64/include/uapi/asm/hwcap.h
> > index 4b9344cba83a..a4bad90a3fa3 100644
> > --- a/arch/arm64/include/uapi/asm/hwcap.h
> > +++ b/arch/arm64/include/uapi/asm/hwcap.h
> > @@ -36,5 +36,10 @@
> > #define HWCAP_FCMA (1 << 14)
> > #define HWCAP_LRCPC (1 << 15)
> > #define HWCAP_DCPOP (1 << 16)
> > +#define HWCAP_SHA3 (1 << 17)
> > +#define HWCAP_SM3 (1 << 18)
> > +#define HWCAP_SM4 (1 << 19)
> > +#define HWCAP_ASIMDDP (1 << 20)
> > +#define HWCAP_SHA512 (1 << 21)
>
> We may be getting some conflicts around these with additional patches
> coming in but not hard to solve. Anyway, whether we are getting pointer
> authentication in or not (probably the latter), I would really like to
> get the first patch in that series merged:
>
> http://lkml.kernel.org/r/1500480092-28480-2-git-send-email-mark.rutland@arm.com
Suzuki -- can you take Mark's patch above and update the documentation to
include the new hwcaps you've added, please?
Will
next prev parent reply other threads:[~2017-10-11 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 9:53 [PATCH v2] arm64: Expose support for optional ARMv8-A features Suzuki K Poulose
2017-10-10 9:53 ` Suzuki K Poulose
2017-10-10 14:35 ` Catalin Marinas
2017-10-10 14:35 ` Catalin Marinas
2017-10-11 12:37 ` Will Deacon [this message]
2017-10-11 12:37 ` Will Deacon
2017-10-11 12:37 ` Suzuki K Poulose
2017-10-11 12:37 ` Suzuki K Poulose
-- strict thread matches above, loose matches on Subject: below --
2017-10-09 17:41 Suzuki K Poulose
2017-10-09 17:41 ` Suzuki K Poulose
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=20171011123705.GE11106@arm.com \
--to=will.deacon@arm.com \
--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.