Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp1246202imm; Fri, 29 Jun 2018 14:16:26 -0700 (PDT) X-Google-Smtp-Source: AAOMgpempLoWqXHdb5odNQP5haCWpTIl5TQtYFuCtgvdDGmIST5KRph0IZ9T331np/gGY0bSNqXJ X-Received: by 2002:a62:ee01:: with SMTP id e1-v6mr15883357pfi.2.1530306986827; Fri, 29 Jun 2018 14:16:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530306986; cv=none; d=google.com; s=arc-20160816; b=QSLV/AcobuWGmiF6A1IQU1G603iz5GPmqZkOJPm+4RoGJ0/acG1YIUpwZkWJWBdnq5 HbTh2ybG6wcKn6wZ2cpoQsth0rBtsJQKS+UWss/qpfa0vEMjOdjDFvaqRhKzh2aYkDH3 WwryjL3jJMsMO0S4nyKLwc6Ndp/kKMgJJarG19RUY/RkV35VEkqtj3xk59UR0aWo243Q bhXhol65SYQiWFS93jBQju8Pc1SNL6Yar2TxuDWid/GAnuqWyIN3szxzA10a141pyRsA 3Anjvmeo5pgz8/B22YUvDh+IkdNAwJjlm3YSU1ODN04wf0oEqOCgickjcCDp+tm+55XL aOsg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=CSxdX8+JXQXM+RcqsoVQZ3u7VJugG7bfwzH6Mw/KDfE=; b=hw/dFVguGozT9YutLtwo2dpc2wj0TFGKIP936jH2V1ITiPZh32xo5Dy/07dfrW9DY3 hbCRc/sLnEaj/FnGSFvljF9nmbWQnx18Rs6pokFlgJQcDB8XUGAj0X487q4bqUWM/Rgg cs+CPnGz2MOe2QjkdH854u+X0r1i+dL3sE6wimQkBcnWMx8qpIGTDvGKWk/0ZdEU1kRz YgF8fc0jfXegvOPP+LHUfWKR254HAMjeJNaiq36GJ5A14CCOoSWAYGT4rnfVab3YINVB Gu1L9yQNd5LF2lul1ET9R/U7oRXAzs2nLUpG6I9EamLZ+fx7xCtRQTei2BR0jcvqbcSU MBYg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r25-v6si9150812pgd.74.2018.06.29.14.16.12; Fri, 29 Jun 2018 14:16:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S937077AbeF2UAs (ORCPT + 99 others); Fri, 29 Jun 2018 16:00:48 -0400 Received: from mga11.intel.com ([192.55.52.93]:19117 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932890AbeF2UAr (ORCPT ); Fri, 29 Jun 2018 16:00:47 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2018 13:00:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,287,1526367600"; d="scan'208";a="241791985" Received: from unknown (HELO localhost.lm.intel.com) ([10.232.112.44]) by fmsmga006.fm.intel.com with ESMTP; 29 Jun 2018 13:00:46 -0700 From: Keith Busch To: Johannes Thumshirn , Christoph Hellwig , Sagi Grimberg , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Keith Busch Subject: [PATCHv3 0/4] nvme trace updates Date: Fri, 29 Jun 2018 13:59:56 -0600 Message-Id: <20180629200000.16171-1-keith.busch@intel.com> X-Mailer: git-send-email 2.13.6 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patch series is based on/inspired by Johannes Thumshirn that improves the nvme trace events. The first one from Sagi is saving the nvme_ctrl in the driver request data so we can reference it in other places, both for this series and future developments. The others are adding and simplifying the nvme traces so we can see information to uniquely identify what hardware the trace event is showing, and filter events for specific hardware. v2 -> v3: Removed unrelated code that leaked into the previous series Added helpers for setting the qid and disk name fields Simplified printing the disk name: it's already null terminated, so don't need to define the limit. Updated change logs Minor code formatting updates Added Reviewed-by for Sagi's patch v1 -> v2: Dropped the blk-mq patch as there were pre-existing ways to get to the desired information without introducing a new API Changelog typo fixups Keith Busch (3): nvme: use hw qid in trace events nvme: add controller name to trace events nvme: add disk name to trace events Sagi Grimberg (1): nvme: cache struct nvme_ctrl reference to struct nvme_request drivers/nvme/host/core.c | 5 +- drivers/nvme/host/fc.c | 1 + drivers/nvme/host/nvme.h | 1 + drivers/nvme/host/pci.c | 2 + drivers/nvme/host/rdma.c | 1 + drivers/nvme/host/trace.c | 11 ++++ drivers/nvme/host/trace.h | 137 +++++++++++++++++++++++++-------------------- drivers/nvme/target/loop.c | 1 + 8 files changed, 93 insertions(+), 66 deletions(-) -- 2.14.3