From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=9mOI=AV=kernelnewbies.org=kernelnewbies-bounces@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=3.0 tests=DKIM_ADSP_CUSTOM_MED,
	DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,
	HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 702B5C433E0
	for <kernelnewbies@archiver.kernel.org>; Fri, 10 Jul 2020 05:30:17 +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 323522063A
	for <kernelnewbies@archiver.kernel.org>; Fri, 10 Jul 2020 05:30:16 +0000 (UTC)
Authentication-Results: mail.kernel.org;
	dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="W3N/K/1K"
DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 323522063A
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-bounces@kernelnewbies.org
Received: from localhost ([::1] helo=shelob.surriel.com)
	by shelob.surriel.com with esmtp (Exim 4.94)
	(envelope-from <kernelnewbies-bounces@kernelnewbies.org>)
	id 1jtlbW-0006Pu-DJ; Fri, 10 Jul 2020 01:29:46 -0400
Received: from mail-qt1-x82d.google.com ([2607:f8b0:4864:20::82d])
 by shelob.surriel.com with esmtps (TLS1.2) tls
 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94)
 (envelope-from <sunshilong369@gmail.com>) id 1jtlbT-0006Po-Ol
 for Kernelnewbies@kernelnewbies.org; Fri, 10 Jul 2020 01:29:43 -0400
Received: by mail-qt1-x82d.google.com with SMTP id a32so3564821qtb.5
 for <Kernelnewbies@kernelnewbies.org>; Thu, 09 Jul 2020 22:29:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=s/scwtooOCExxZ2jY+qUy7/rDidk1N21p8LTNAzkr+0=;
 b=W3N/K/1K8ir1G6TvphEzLLjRxR59UNEGJ88yvyq1Qe0jXbhE5td1h2ztbt7OmPlv+U
 A+qGLvH+bk7eJo7HMe/gdeQMQsmcUTp4gnJdhxRTGVg4EE3/ebRrgLLnDlNqZ+kH3F0Y
 ljtJ9tGBsAXLKrhO3kbS9HNd0hWp5T+gWmUVW74Oggut2GXQpxe6oEfVU2awxp9aQ0fY
 R/TIkAdEYRJlzvdB18KiA4yh7ZjanpGKKNCcgmK+hKmrLD1XSv0lDMOLy++8QtngNz9l
 dTgEvWch3dEdZZgGh8v0Yk3Mm28OOP2y813du8kfDFIDZtn+dQHGWrqT7WAvKctQmRNw
 dByg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=s/scwtooOCExxZ2jY+qUy7/rDidk1N21p8LTNAzkr+0=;
 b=VUDM8Ix81oT5Hz3Dbtto3u6V+pHrgtau7GTbip2d6O2caD15M3wQHgciw1YJ1WFTfW
 +b77sjeWH503yEicZ9TvJSs3PbqFhlVOZnGcy29RPPki8JoFBIgFzZslgleVmzQfIl4n
 yiLj4qPTYPf0f788NJRHec2PT18Kn0IsgSk7mp5OWbq4p5cq9PCtxugUgkWSaRRmQhzZ
 f6ky4IE3PeXlBHcSmlxQ6TGMDTbownTU3lWp2ZYspkPKRb3xFDqjaAnVpfRQRimm45yv
 N19el/+KvwKMOeNGAkjw89Kb8P04kCo3J0kYUdCMaAEMeGAeIDYmvd6yBUPC6GhmkWBy
 PU3w==
X-Gm-Message-State: AOAM53047QuxwZkFAsCik4ZvlhcLRm0GAccRgn/N6MrPs3ImKY8Z3XId
 jDJUApFWIhrVjA1tKHvnD1YTk1UIkuvM4SKuDkrKM47tMQvYrg==
X-Google-Smtp-Source: ABdhPJzrKfW0fSvx5ebKKCTEI8Hdc5QtBQwRtM2ANn8GgYlBELtn1+kRdhHoFzVh3aq3RzPc8927HzNM33r9N+rBlZk=
X-Received: by 2002:aed:2e07:: with SMTP id j7mr72826752qtd.338.1594358981087; 
 Thu, 09 Jul 2020 22:29:41 -0700 (PDT)
MIME-Version: 1.0
From: =?UTF-8?B?5a2Z5LiW6b6ZIHN1bnNoaWxvbmc=?= <sunshilong369@gmail.com>
Date: Fri, 10 Jul 2020 13:29:29 +0800
Message-ID: <CAAvDm6bRTfHzWysY0=pw7beB6GmXY7PN0h-xv7HMGDY3VACNcA@mail.gmail.com>
Subject: Why are there "<IRQ>" and "</IRQ>" in the call trace section? What
 does them imply?
To: kernelnewbies <Kernelnewbies@kernelnewbies.org>
X-BeenThere: kernelnewbies@kernelnewbies.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Learn about the Linux kernel <kernelnewbies.kernelnewbies.org>
List-Unsubscribe: <https://lists.kernelnewbies.org/mailman/options/kernelnewbies>, 
 <mailto:kernelnewbies-request@kernelnewbies.org?subject=unsubscribe>
List-Archive: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/>
List-Post: <mailto:kernelnewbies@kernelnewbies.org>
List-Help: <mailto:kernelnewbies-request@kernelnewbies.org?subject=help>
List-Subscribe: <https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies>, 
 <mailto:kernelnewbies-request@kernelnewbies.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kernelnewbies-bounces@kernelnewbies.org

Hi, list

As the subject, here is the related log:
[72873.713472] Call Trace:
[72873.713473]  <IRQ>
[72873.713474]  switch_mm_irqs_off+0x31b/0x4e0
[72873.713475]  xnarch_switch_to+0x2f/0x80
[72873.713476]  ___xnsched_run.part.74+0x154/0x480
[72873.713476]  ___xnsched_run+0x35/0x50
[72873.713477]  xnintr_irq_handler+0x346/0x4c0
[72873.713478]  ? xnintr_core_clock_handler+0x1b6/0x360
[72873.713479]  dispatch_irq_head+0x8e/0x110
[72873.713479]  ? xnintr_irq_handler+0x5/0x4c0
[72873.713481]  ? dispatch_irq_head+0x8e/0x110
[72873.713482]  __ipipe_dispatch_irq+0xd9/0x1c0
[72873.713483]  __ipipe_handle_irq+0x86/0x1e0
[72873.713483]  common_interrupt+0xf/0x2c
[72873.713484]  </IRQ>

Maybe, the later one(i.e. </IRQ>) implies there was an interrupt
request and the common_interuppt() function handler it.
Am I right?

But what about the former one(i.e. <IRQ>)?

Thank you for your attention to this matter.

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies