From: Jan Luebbe <jlu@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Jan Luebbe <jlu@pengutronix.de>
Subject: [ptxdist] [PATCH] blktrace: add new package
Date: Tue, 25 Jun 2019 12:14:36 +0200 [thread overview]
Message-ID: <20190625101436.29088-1-jlu@pengutronix.de> (raw)
Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
---
rules/blktrace.in | 8 +++++++
rules/blktrace.make | 66 +++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 74 insertions(+)
create mode 100644 rules/blktrace.in
create mode 100644 rules/blktrace.make
diff --git a/rules/blktrace.in b/rules/blktrace.in
new file mode 100644
index 000000000000..69335e2e4288
--- /dev/null
+++ b/rules/blktrace.in
@@ -0,0 +1,8 @@
+## SECTION=disk_and_file
+
+config BLKTRACE
+ tristate
+ prompt "blktrace"
+ help
+ Collects and parses block IO traces using the CONFIG_BLK_DEV_IO_TRACE
+ kernel feature.
diff --git a/rules/blktrace.make b/rules/blktrace.make
new file mode 100644
index 000000000000..2b41afdf2c7c
--- /dev/null
+++ b/rules/blktrace.make
@@ -0,0 +1,66 @@
+# -*-makefile-*-
+#
+# Copyright (C) 2019 by Jan Luebbe <jlu@pengutronix.de>
+#
+# See CREDITS for details about who has contributed to this project.
+#
+# For further information about the PTXdist project and license conditions
+# see the README file.
+#
+
+#
+# We provide this package
+#
+PACKAGES-$(PTXCONF_BLKTRACE) += blktrace
+
+#
+# Paths and names
+#
+BLKTRACE_VERSION := 1.2.0
+BLKTRACE_MD5 := b9a80b7cc0a50f7a96d34c570ab8224d
+BLKTRACE := blktrace-$(BLKTRACE_VERSION)
+BLKTRACE_SUFFIX := tar.bz2
+BLKTRACE_URL := http://brick.kernel.dk/snaps/$(BLKTRACE).$(BLKTRACE_SUFFIX)
+BLKTRACE_SOURCE := $(SRCDIR)/$(BLKTRACE).$(BLKTRACE_SUFFIX)
+BLKTRACE_DIR := $(BUILDDIR)/$(BLKTRACE)
+BLKTRACE_LICENSE := GPL-2.0-only
+
+# ----------------------------------------------------------------------------
+# Prepare
+# ----------------------------------------------------------------------------
+
+BLKTRACE_CONF_TOOL := NO
+BLKTRACE_MAKE_PAR := NO
+BLKTRACE_MAKE_OPT := $(CROSS_ENV) blktrace blkparse
+
+# ----------------------------------------------------------------------------
+# Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/blktrace.install:
+ @$(call targetinfo)
+ @$(call touch)
+
+# ----------------------------------------------------------------------------
+# Target-Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/blktrace.targetinstall:
+ @$(call targetinfo)
+
+ @$(call install_init, blktrace)
+ @$(call install_fixup, blktrace,PRIORITY,optional)
+ @$(call install_fixup, blktrace,SECTION,base)
+ @$(call install_fixup, blktrace,AUTHOR,"Jan Luebbe <jlu@pengutronix.de>")
+ @$(call install_fixup, blktrace,DESCRIPTION,missing)
+
+ @$(call install_copy, blktrace, 0, 0, 0755, $(BLKTRACE_DIR)/blkparse, \
+ /usr/bin/blkparse)
+ @$(call install_copy, blktrace, 0, 0, 0755, $(BLKTRACE_DIR)/blktrace, \
+ /usr/sbin/blktrace)
+
+ @$(call install_finish, blktrace)
+
+ @$(call touch)
+
+# vim: syntax=make
--
2.11.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-06-25 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 10:14 Jan Luebbe [this message]
2019-06-25 10:24 ` Michael Olbrich
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=20190625101436.29088-1-jlu@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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