All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: George Pee <georgepee@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	"Kirill A. Shutemov" <kirill.shtuemov@linux.intel.com>,
	Austin Kim <austindh.kim@gmail.com>,
	Ard Biesheuvel <ardb@kernel.org>, Mike Rapoport <rppt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Report support for optional ARMv8.2 half-precision floating point extension
Date: Fri, 9 Sep 2022 15:07:04 +0100	[thread overview]
Message-ID: <YxtIiBvAGs2vAl1P@arm.com> (raw)
In-Reply-To: <CAKj0CMv1EY5YCeQ4G6PnGP=XfELJkkN5BaN8W1TGe0fOTXfJBw@mail.gmail.com>

On Fri, Sep 09, 2022 at 08:34:26AM -0500, George Pee wrote:
> Adding the hwcap was part of the diagnosis process-- I added it just
> to make sure that the cpu in question supported the optional
> extension.
> It seems like it could be useful to be able to check for support in
> /proc/cpuinfo.

Ah, I wasn't aware that the feature doesn't work on arm32. I don't think
it makes sense to expose a hwcap bit to user in this case.

-- 
Catalin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: George Pee <georgepee@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	"Kirill A. Shutemov" <kirill.shtuemov@linux.intel.com>,
	Austin Kim <austindh.kim@gmail.com>,
	Ard Biesheuvel <ardb@kernel.org>, Mike Rapoport <rppt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Report support for optional ARMv8.2 half-precision floating point extension
Date: Fri, 9 Sep 2022 15:07:04 +0100	[thread overview]
Message-ID: <YxtIiBvAGs2vAl1P@arm.com> (raw)
In-Reply-To: <CAKj0CMv1EY5YCeQ4G6PnGP=XfELJkkN5BaN8W1TGe0fOTXfJBw@mail.gmail.com>

On Fri, Sep 09, 2022 at 08:34:26AM -0500, George Pee wrote:
> Adding the hwcap was part of the diagnosis process-- I added it just
> to make sure that the cpu in question supported the optional
> extension.
> It seems like it could be useful to be able to check for support in
> /proc/cpuinfo.

Ah, I wasn't aware that the feature doesn't work on arm32. I don't think
it makes sense to expose a hwcap bit to user in this case.

-- 
Catalin

  reply	other threads:[~2022-09-09 14:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 14:13 [PATCH] Report support for optional ARMv8.2 half-precision floating point extension george pee
2022-09-01 14:13 ` george pee
2022-09-09 11:39 ` Catalin Marinas
2022-09-09 11:39   ` Catalin Marinas
2022-09-09 13:35   ` George Pee
2022-09-09 13:35     ` George Pee
2022-09-09 12:46 ` Robin Murphy
2022-09-09 12:46   ` Robin Murphy
2022-09-09 13:34   ` George Pee
2022-09-09 13:34     ` George Pee
2022-09-09 14:07     ` Catalin Marinas [this message]
2022-09-09 14:07       ` Catalin Marinas
2022-09-09 14:57       ` George Pee
2022-09-09 14:57         ` George Pee
2022-09-09 15:05         ` Catalin Marinas
2022-09-09 15:05           ` Catalin Marinas
2022-09-12 13:05           ` Russell King (Oracle)
2022-09-12 13:05             ` Russell King (Oracle)
2022-09-12 18:09             ` George Pee
2022-09-12 18:09               ` George Pee
2022-09-09 14:17     ` Robin Murphy
2022-09-09 14:17       ` Robin Murphy
2022-09-09 14:54       ` George Pee
2022-09-09 14:54         ` George Pee

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=YxtIiBvAGs2vAl1P@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=ardb@kernel.org \
    --cc=austindh.kim@gmail.com \
    --cc=georgepee@gmail.com \
    --cc=kirill.shtuemov@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robin.murphy@arm.com \
    --cc=rppt@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.