Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andre Kempe <Andre.Kempe@arm.com>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Cc: "martin@martin.st" <martin@martin.st>
Subject: [FFmpeg-devel] arm64: Add Armv8.3-A PAC support to assembly files
Date: Wed, 9 Feb 2022 15:27:35 +0000
Message-ID: <DBBPR08MB5547972C9F76F512506305B6EF2E9@DBBPR08MB5547.eurprd08.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

Hi everyone,

This patch adds signing and validation of LinkRegister when storing to and
Loading from stack using Pointer Authentication Codes (PACs).

PAC support is turned on or off at compile time based on the presence of
the __ARM_FEATURE_PAC_DEFAULT feature macro. Without PAC enabled
at compile time, no additional instruction will be emitted at all.

A binary compiled with PAC support can be executed on processors
without PAC support because the instructions are defined in NOP space.

Regression tested in in a PAC-enabled environment - no issues. Could
someone please have a look and give feedback?

Thanks + Best Regards,
André

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #2: arm64-Add-Armv8.3-A-PAC-support-to-assembly-files.patch --]
[-- Type: application/octet-stream, Size: 9829 bytes --]

[-- Attachment #3: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

                 reply	other threads:[~2022-02-09 15:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DBBPR08MB5547972C9F76F512506305B6EF2E9@DBBPR08MB5547.eurprd08.prod.outlook.com \
    --to=andre.kempe@arm.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=martin@martin.st \
    /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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git