public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "qiansiqiu1996 at 163 dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/28039] Can systemtap support sparc arch?
Date: Wed, 07 Jul 2021 03:17:18 +0000	[thread overview]
Message-ID: <bug-28039-6586-RwlpHNQJfj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28039-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28039

--- Comment #2 from qiansiqiu1996 at 163 dot com ---
(In reply to William Cohen from comment #1)
> I added the support for aarch64 to systemtap. It significant work to add
> architecture support for a new platform.  We welcome outside patches to
> support new architectures, but it is unlikely that we are going to develop
> one for SPARC.  One could use the changes in systemtap for aarch64 as
> suggestions of where changes need to be made to support a new architecture:
> 
> https://sourceware.org/git/?p=systemtap.
> git&a=search&h=HEAD&st=commit&s=aarch64
> 
> In the kernels sparc has HAVE_KPROBES in linux/arch/sparc/Kconfig, so
> kprobes are implemented.  However, I don't know have tested that is. I found
> some issues with the aarch64 implementation of kprobes when working on the
> systemtap aarch64 support.

Dear good brother,are you the developer of systemtap?Can you add the support of
sparc?Thank you very much!
I read the source of tapset and runtime,i think we can add the register.h and
stp files to support a new architecture.
I know it support aarch64(i already use),but what i say is sparc.

Thank you very much!love you!

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2021-07-07  3:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01  3:26 [Bug runtime/28039] New: " qiansiqiu1996 at 163 dot com
2021-07-01 17:13 ` [Bug runtime/28039] " wcohen at redhat dot com
2021-07-07  3:17 ` qiansiqiu1996 at 163 dot com [this message]
2021-07-08 17:44 ` wcohen at redhat dot com
2021-07-12 20:41 ` wcohen at redhat dot com
2023-11-29 16:34 ` wcohen at redhat dot com
2023-12-06 15:05 ` sam at gentoo dot org

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=bug-28039-6586-RwlpHNQJfj@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).