From: Vineet Gupta <vgupta@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
arcml <linux-snps-arc@lists.infradead.org>,
abrodkin@synopsys.com, "geomatsi@gmail.com" <geomatsi@gmail.com>
Subject: [GIT PULL] ARC changes for 5.19-rc1
Date: Wed, 25 May 2022 20:40:39 -0700 [thread overview]
Message-ID: <a22af786-288f-92ad-79a0-0f40768cfdbc@kernel.org> (raw)
Hi Linus,
Please pull.
Thx,
-Vineet
--------------->
The following changes since commit af2d861d4cd2a4da5137f795ee3509e6f944a25b:
Linux 5.18-rc4 (2022-04-24 14:51:22 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git/
tags/arc-5.19-rc1
for you to fetch changes up to 6aa98f6217861889523e38b0141c8c71b2ef8a83:
ARC: bpf: define uapi for BPF_PROG_TYPE_PERF_EVENT program type
(2022-04-26 09:35:28 -0700)
----------------------------------------------------------------
ARC changes for 5.19-rc1
- Basic eBPF support (Sergey)
----------------------------------------------------------------
Sergey Matyukevich (4):
ARC: enable HAVE_REGS_AND_STACK_ACCESS_API feature
ARC: implement syscall tracepoints
ARC: disasm: handle ARCv2 case in kprobe get/set functions
ARC: bpf: define uapi for BPF_PROG_TYPE_PERF_EVENT program type
arch/arc/Kconfig | 2 +
arch/arc/include/asm/perf_event.h | 4 +
arch/arc/include/asm/ptrace.h | 27 ++++++
arch/arc/include/asm/syscall.h | 2 +
arch/arc/include/asm/thread_info.h | 5 +-
arch/arc/include/uapi/asm/bpf_perf_event.h | 9 ++
arch/arc/kernel/disasm.c | 64 ++++++++++++-
arch/arc/kernel/entry.S | 12 +--
arch/arc/kernel/ptrace.c | 140
++++++++++++++++++++++++++++-
9 files changed, 253 insertions(+), 12 deletions(-)
create mode 100644 arch/arc/include/uapi/asm/bpf_perf_event.h
next reply other threads:[~2022-05-26 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 3:40 Vineet Gupta [this message]
2022-05-27 0:32 ` pr-tracker-bot
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=a22af786-288f-92ad-79a0-0f40768cfdbc@kernel.org \
--to=vgupta@kernel.org \
--cc=abrodkin@synopsys.com \
--cc=geomatsi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®