From: Gurudas Pai <gurudas.pai@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v2 0/9] sparc64: Support 47-bit physical addresses.
Date: Sat, 12 Oct 2013 02:05:40 +0000 [thread overview]
Message-ID: <5258AE74.5050200@oracle.com> (raw)
In-Reply-To: <20130930.123130.354302574443157859.davem@davemloft.net>
On 10/11/2013 02:54 PM, David Miller wrote:
> From: Gurudas Pai <gurudas.pai@oracle.com>
> Date: Fri, 11 Oct 2013 14:26:52 -0700
>
>> CPU CAPS: [flush,stbar,swap,muldiv,v9,blkinit,n2,mul32]
>> CPU CAPS: [div32,v8plus,popc,vis,vis2,ASIBlkInit,fmaf,ima]
> Hmmm, lots of capabilities missing I thought would be there.
> For example, all the crypto opcodes.
>
> Are they really not there in the T5 chips? Indeed they don't
> show up in the hwcap-list of the cpu MDESC node :-/
This from sparc64-x, not t5.
Thanks,
-Guru
next prev parent reply other threads:[~2013-10-12 2:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 16:31 [PATCH v2 0/9] sparc64: Support 47-bit physical addresses David Miller
2013-09-30 20:14 ` Gurudas Pai
2013-09-30 23:07 ` David Miller
2013-09-30 23:47 ` Gurudas Pai
2013-09-30 23:51 ` David Miller
2013-10-01 0:42 ` Gurudas Pai
2013-10-01 20:11 ` David Miller
2013-10-01 23:08 ` Gurudas Pai
2013-10-02 1:20 ` Gurudas Pai
2013-10-02 5:11 ` David Miller
2013-10-02 18:14 ` David Miller
2013-10-02 18:25 ` David Miller
2013-10-02 19:38 ` Gurudas Pai
2013-10-02 20:17 ` David Miller
2013-10-02 21:02 ` Gurudas Pai
2013-10-02 21:18 ` David Miller
2013-10-04 2:07 ` Gurudas Pai
2013-10-04 2:16 ` Gurudas Pai
2013-10-04 15:45 ` Bob Picco
2013-10-04 16:24 ` Bob Picco
2013-10-04 18:00 ` David Miller
2013-10-07 16:07 ` Bob Picco
2013-10-07 16:08 ` David Miller
2013-10-08 13:42 ` Bob Picco
2013-10-09 19:18 ` David Miller
2013-10-09 20:03 ` David Miller
2013-10-10 14:19 ` Bob Picco
2013-10-11 21:26 ` Gurudas Pai
2013-10-11 21:54 ` David Miller
2013-10-12 2:05 ` Gurudas Pai [this message]
2013-10-12 5:06 ` David Miller
2013-10-23 1:18 ` Gurudas Pai
2013-10-23 5:28 ` David Miller
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=5258AE74.5050200@oracle.com \
--to=gurudas.pai@oracle.com \
--cc=sparclinux@vger.kernel.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.