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;
MIME-Version: 1.0
References: <20220210225222.260069-1-shy828301@gmail.com> <164459883724.122482.1096803254957441815.b4-ty@kernel.dk>
In-Reply-To: <164459883724.122482.1096803254957441815.b4-ty@kernel.dk>
From:   Yang Shi <shy828301@gmail.com>
Date:   Fri, 11 Feb 2022 12:56:21 -0800
Message-ID: <CAHbLzkrNhPUjs+NE=e8-t9qOnDLkKeR5J_r2eQQdOarZhhGTFg@mail.gmail.com>
Subject: Re: [v8 PATCH] block: introduce block_rq_error tracepoint
To:     Jens Axboe <axboe@kernel.dk>
Cc:     Steven Rostedt <rostedt@goodmis.org>,
        Cong Wang <xiyou.wangcong@gmail.com>,
        Chaitanya Kulkarni <kch@nvidia.com>,
        Christoph Hellwig <hch@infradead.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-block@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Feb 11, 2022 at 9:00 AM Jens Axboe <axboe@kernel.dk> wrote:
>
> 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

Thank you!

>
> Best regards,
> --
> Jens Axboe
>
>