From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>,
Peter Zijlstra <peterz@infradead.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>,
Ming Lei <ming.lei@redhat.com>
Subject: [PATCH 0/3] block: model freeze/enter queue as lock for lockdep
Date: Wed, 23 Oct 2024 17:54:32 +0800 [thread overview]
Message-ID: <20241023095438.3451156-1-ming.lei@redhat.com> (raw)
Hello,
The 1st patch adds non_owner variants of start_freeze/unfreeze queue
API.
The 2nd patch applies the non_owner variants on nvme_freeze() & nvme_unfreeze().
The 3rd patch models freeze/enter queue as lock for lockdep support.
Ming Lei (3):
blk-mq: add non_owner variant of start_freeze/unfreeze queue APIs
nvme: core: switch to non_owner variant of start_freeze/unfreeze queue
block: model freeze & enter queue as lock for supporting lockdep
block/blk-core.c | 18 +++++++++++++++--
block/blk-mq.c | 43 +++++++++++++++++++++++++++++++++++++---
block/blk.h | 29 ++++++++++++++++++++++++---
block/genhd.c | 15 ++++++++++----
drivers/nvme/host/core.c | 4 ++--
include/linux/blk-mq.h | 2 ++
include/linux/blkdev.h | 6 ++++++
7 files changed, 103 insertions(+), 14 deletions(-)
--
2.46.0
next reply other threads:[~2024-10-23 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 9:54 Ming Lei [this message]
2024-10-23 9:54 ` [PATCH 1/3] blk-mq: add non_owner variant of start_freeze/unfreeze queue APIs Ming Lei
2024-10-23 12:19 ` Christoph Hellwig
2024-10-23 9:54 ` [PATCH 2/3] nvme: core: switch to non_owner variant of start_freeze/unfreeze queue Ming Lei
2024-10-23 12:21 ` Christoph Hellwig
2024-10-24 1:43 ` Ming Lei
2024-10-24 5:00 ` Christoph Hellwig
2024-10-24 6:43 ` Ming Lei
2024-10-23 9:54 ` [PATCH 3/3] block: model freeze & enter queue as lock for supporting lockdep Ming Lei
2024-10-23 12:22 ` Christoph Hellwig
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=20241023095438.3451156-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=boqun.feng@gmail.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®