Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Jens Axboe <axboe@kernel.dk>
To:     rostedt@goodmis.org, Yang Shi <shy828301@gmail.com>,
        xiyou.wangcong@gmail.com, kch@nvidia.com, hch@infradead.org
Cc:     linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
In-Reply-To: <20220210225222.260069-1-shy828301@gmail.com>
References: <20220210225222.260069-1-shy828301@gmail.com>
Subject: Re: [v8 PATCH] block: introduce block_rq_error tracepoint
Message-Id: <164459883724.122482.1096803254957441815.b4-ty@kernel.dk>
Date:   Fri, 11 Feb 2022 10:00:37 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 10 Feb 2022 14:52:22 -0800, Yang Shi wrote:
> Currently, rasdaemon uses the existing tracepoint block_rq_complete
> and filters out non-error cases in order to capture block disk errors.
> 
> But there are a few problems with this approach:
> 
> 1. Even kernel trace filter could do the filtering work, there is
>    still some overhead after we enable this tracepoint.
> 
> [...]

Applied, thanks!

[1/1] block: introduce block_rq_error tracepoint
      commit: d5869fdc189f0f12a954a48d58a48104a2f5d044

Best regards,
-- 
Jens Axboe