From: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
To: linux-btrace@vger.kernel.org
Subject: [RFC PATCH 02/39] blktrace_api: add new trace definition
Date: Thu, 05 Nov 2020 02:40:01 +0000 [thread overview]
Message-ID: <20201105024038.5831-3-chaitanya.kulkarni@wdc.com> (raw)
This patch adds new structure similar to struct blk_trace to support
block trace extensions.
Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
---
include/linux/blktrace_api.h | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/include/linux/blktrace_api.h b/include/linux/blktrace_api.h
index 3b6ff5902edc..bc154ff2522a 100644
--- a/include/linux/blktrace_api.h
+++ b/include/linux/blktrace_api.h
@@ -29,6 +29,24 @@ struct blk_trace {
atomic_t dropped;
};
+struct blk_trace_ext {
+ int trace_state;
+ struct rchan *rchan;
+ unsigned long __percpu *sequence;
+ unsigned char __percpu *msg_data;
+ u64 act_mask;
+ u32 prio_mask;
+ u64 start_lba;
+ u64 end_lba;
+ u32 pid;
+ u32 dev;
+ struct dentry *dir;
+ struct dentry *dropped_file;
+ struct dentry *msg_file;
+ struct list_head running_ext_list;
+ atomic_t dropped;
+};
+
struct blkcg;
extern int blk_trace_ioctl(struct block_device *, unsigned, char __user *);
--
2.22.1
next reply other threads:[~2020-11-05 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 2:40 Chaitanya Kulkarni [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-25 7:01 [RFC PATCH 00/39] blktrace: add block trace extension support Chaitanya Kulkarni
2021-02-25 7:01 ` [RFC PATCH 02/39] blktrace_api: add new trace definition Chaitanya Kulkarni
2021-02-26 4:33 ` Damien Le Moal
2020-08-25 22:09 Chaitanya Kulkarni
2020-03-23 16:29 Chaitanya Kulkarni
2019-11-20 4:24 Chaitanya Kulkarni
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=20201105024038.5831-3-chaitanya.kulkarni@wdc.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=linux-btrace@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.