From: "Yu, Fenghua" <fenghua.yu@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Luck, Tony" <tony.luck@intel.com>,
"Li, Xiaoyao" <xiaoyao.li@intel.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: RE: [PATCH v3 4/4] Documentation/admin-guide: Change doc for split_lock_detect parameter
Date: Sat, 21 Nov 2020 04:36:36 +0000 [thread overview]
Message-ID: <0cec6aea4dd14171a216ceb7960f6996@intel.com> (raw)
In-Reply-To: <171caa46-8431-ee58-2cad-954cb63cb1f3@infradead.org>
Hi, Randy,
> >>> + for bus lock detection. 0 < N <= HZ/2 and
> >>> + N is approximate. Only applied to non-root
> >>> + users.
> >>
> >> Sorry, but I don't know what this means. I think it's the "and N is
> >> appropriate"
> >> that is confusing me.
> >>
> >> 0 < N <= HZ/2 and N is appropriate.
> >
> > You are right. I will remove "and N is appropriate" in the next version.
> >
> > Could you please ack this patch? Can I add Acked-by from you in the
> updated patch?
> >
> > Thank you very much for your review!
>
> Sure, no problem.
>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
Really appreciate your review!
-Fenghua
prev parent reply other threads:[~2020-11-21 4:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 2:36 [PATCH v3 0/4] x86/bus_lock: Enable bus lock detection Fenghua Yu
2020-11-21 2:36 ` [PATCH v3 1/4] x86/cpufeatures: Enumerate #DB for " Fenghua Yu
2020-11-21 2:36 ` [PATCH v3 2/4] x86/bus_lock: Handle warn and fatal in #DB for bus lock Fenghua Yu
2020-11-21 2:36 ` [PATCH v3 3/4] x86/bus_lock: Set rate limit " Fenghua Yu
2020-11-21 2:36 ` [PATCH v3 4/4] Documentation/admin-guide: Change doc for split_lock_detect parameter Fenghua Yu
2020-11-21 3:31 ` Randy Dunlap
2020-11-21 4:09 ` Yu, Fenghua
2020-11-21 4:12 ` Randy Dunlap
2020-11-21 4:36 ` Yu, Fenghua [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=0cec6aea4dd14171a216ceb7960f6996@intel.com \
--to=fenghua.yu@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).