From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 091E1C4332F for ; Mon, 18 Oct 2021 10:13:02 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9831860E90 for ; Mon, 18 Oct 2021 10:13:01 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 9831860E90 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1mcPdP-0005vb-V8; Mon, 18 Oct 2021 06:12:47 -0400 Received: from mail-oi1-x22a.google.com ([2607:f8b0:4864:20::22a]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1mcPdM-0005vG-BF for kernelnewbies@kernelnewbies.org; Mon, 18 Oct 2021 06:12:44 -0400 Received: by mail-oi1-x22a.google.com with SMTP id m67so23672958oif.6 for ; Mon, 18 Oct 2021 03:12:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sWKFhQFxpK/vC/aWZPtQ7UBsMoQZKBgpdFvLIyxNmBQ=; b=g3kr838+trl8Nry0YjKh9Zayp8efXtT9O3CT48oYIGVBje+PItZDfKvJADoB/9YjDx GQM6psr6Zrg5v/+a9/uDExIsUAyLCq1mpVIQK94AkOiBLwTEZ4DnQStJBBaOt4nOmO/q WeNIHWchlBKsLyZ8K/03BdtfXk7OGU8PJCRUJEbkhlUATyw4uyzgpP2bg9uGwT3besBc t2ypW6zg+rOJRr3xVraLNPGUjpZ+OM4ya4YL/2ru5ih46T6XC7vJx/3rzuGiqdL+ezbj Llhe7L2vOuA5CaKSK9Hh33NP3+K0YMWGVslUD6KiiVr48asjXRnp3fT6rZ4iaRjKEygx YsRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sWKFhQFxpK/vC/aWZPtQ7UBsMoQZKBgpdFvLIyxNmBQ=; b=QBf9InT7RetTtb6nr1kM71DFHE1/O/NmYgDjpYqwt2xyl7dujt2zhWXTlGlHg/hEQY 2s+rp6rru6m0bPuj38mCrqQ/mVLmhl7yhI7EFEH6XvPVa8hGn5L6vrVwiVqq2CkR4gSS 6H6FM73A/LzCAmj+oMHuYmAsiPBrxnQsCY63Myvn8WFUKnGCSy0HAzc8PTLtLqoYCHD8 ga/IbMrB7Fx1uDlMnsDSCCiyP5bhhxb/fEliiDDLLYm86WA3MPmn0YWEBxk2d01Dur7c rKR8GIre7YolnO9W10USNvaHGYAyxH2JH+fr2YXKFplVaUpINKlag0+fIOJoYJBw5n20 NHGA== X-Gm-Message-State: AOAM5331NwjSI/q6Ah4R1NsvcvbcU4Vz3wfmBHlcrRb65e5tdNydTy69 Ui/9/+4B4uVi0gEzR7AiOPchYufh8IOHdwfEisUqPm3R X-Google-Smtp-Source: ABdhPJwDL/V5HshhjAs8DV6IrZ9kgNNyOB0QNZf9ooVXyTmNdrXEZcDO0jXPkP5Q5ovHxZYbEZJEqfqi86DPI1dC8ko= X-Received: by 2002:a05:6808:57:: with SMTP id v23mr18994672oic.172.1634551963135; Mon, 18 Oct 2021 03:12:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: FMDF Date: Mon, 18 Oct 2021 12:12:15 +0200 Message-ID: Subject: Re: Any tracing mechanism can track the executed instructions of a user process in the kernel? To: Dongliang Mu Cc: Greg KH , Brendan Gregg , Pavel Skripkin , Dan Carpenter , kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6943176713399114682==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============6943176713399114682== Content-Type: multipart/alternative; boundary="00000000000021337305ce9dc916" --00000000000021337305ce9dc916 Content-Type: text/plain; charset="UTF-8" On Mon, 18 Oct 2021, 11:48 FMDF, wrote: Now I recall that, by using Perf, somehow I was able to go interactively > down to the assembly code and see where it was stuck in an endless loop. > Ah, yes. The loop was somewhere into glibc. So I'm not sure if it is possible to see the kernel assembly with it (it seems highly not probable). I guess that you still need GDB and friends for that. Regards, Fabio > --00000000000021337305ce9dc916 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, 18 Oct 2021, 11:48 FMDF, <fmdefrancesco@gmail.com> wrote:

Now I recall t= hat, by using Perf,=C2=A0 somehow I was able to go interactively down to th= e assembly code and see where it was stuck in an endless loop.
<= /blockquote>

Ah, yes. Th= e loop was somewhere into glibc. So I'm not sure if it is possible to s= ee the kernel assembly with it (it seems highly not probable).

I guess that you still need GDB and = friends for that.

Regard= s,

Fabio
--00000000000021337305ce9dc916-- --===============6943176713399114682== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============6943176713399114682==--