From: "liupeng (DM)" <liupeng256@huawei.com>
To: Marco Elver <elver@google.com>
Cc: <glider@google.com>, <dvyukov@google.com>, <corbet@lwn.net>,
<sumit.semwal@linaro.org>, <christian.koenig@amd.com>,
<akpm@linux-foundation.org>, <kasan-dev@googlegroups.com>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linaro-mm-sig@lists.linaro.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH RFC 3/3] kfence: Make test case compatible with run time set sample interval
Date: Wed, 26 Jan 2022 20:12:58 +0800 [thread overview]
Message-ID: <4bb5e98f-83fe-4406-6a50-f3626af8cebb@huawei.com> (raw)
In-Reply-To: <CANpmjNNc6F7tRVn=UqLaW0WAgTr67XFm=CUu5X2D0Xbt3nKXwA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
On 2022/1/24 20:21, Marco Elver wrote:
> On Mon, 24 Jan 2022 at 13:19, liupeng (DM)<liupeng256@huawei.com> wrote:
> [...]
>> When KFENCE pool size can be adjusted by boot parameters(assumption),
>> automatically test and train KFENCE may be useful. So far, exporting
>> kfence.sample_interval is not necessary.
> I'm not opposed to the patch (I've also run into this issue, but not
> too frequently) - feel free to just send it with EXPORT_SYMBOL_GPL.
>
> Thanks,
> -- Marco
> .
Good, I will send a revised patch latter.
Thanks,
-- Peng Liu
.
[-- Attachment #2: Type: text/html, Size: 1131 bytes --]
prev parent reply other threads:[~2022-01-26 12:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 2:52 [PATCH RFC 0/3] Add a module parameter to adjust kfence objects Peng Liu
2022-01-24 2:52 ` [PATCH RFC 1/3] kfence: " Peng Liu
2022-01-24 8:19 ` Marco Elver
2022-01-24 11:24 ` liupeng (DM)
2022-01-24 11:32 ` Dmitry Vyukov
2022-01-24 11:45 ` Marco Elver
2022-01-24 11:55 ` Marco Elver
2022-01-26 12:09 ` liupeng (DM)
2022-01-24 2:52 ` [PATCH RFC 2/3] kfence: Optimize branches prediction when sample interval is zero Peng Liu
2022-01-24 8:20 ` Marco Elver
2022-01-24 2:52 ` [PATCH RFC 3/3] kfence: Make test case compatible with run time set sample interval Peng Liu
2022-01-24 8:25 ` Marco Elver
2022-01-24 12:18 ` liupeng (DM)
2022-01-24 12:21 ` Marco Elver
2022-01-26 12:12 ` liupeng (DM) [this message]
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=4bb5e98f-83fe-4406-6a50-f3626af8cebb@huawei.com \
--to=liupeng256@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sumit.semwal@linaro.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