From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>,
"Murilo Opsfelder Araujo" <muriloo@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 1/5] rfi-flush: Move the logic to avoid a redo into the debugfs code
Date: Fri, 16 Mar 2018 13:42:07 -0300 [thread overview]
Message-ID: <bd359480-5b04-91d5-2a9e-9129c6772c41@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180316095200.78f31a50@naga.suse.cz>
Hi Murilo and Michal,
On 03/16/2018 05:52 AM, Michal Suchánek wrote:
>> Do we need to take into account if no_rfi_flush == true?
> I think it makes sense you are able to override that using debugfs.
>
> It's interface used for diagnostics and testing.
>
> If this was in sysfs it would be a different story.
Yes, I agree. The debugfs is way to override the cmdline option.
Thanks for looking carefully at this :)
cheers,
Mauricio
next prev parent reply other threads:[~2018-03-16 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 22:40 [PATCH v3 0/5] Setup RFI flush after PowerVM LPM migration Mauricio Faria de Oliveira
2018-03-14 22:40 ` [PATCH v3 1/5] rfi-flush: Move the logic to avoid a redo into the debugfs code Mauricio Faria de Oliveira
2018-03-15 20:36 ` Murilo Opsfelder Araujo
2018-03-16 8:52 ` Michal Suchánek
2018-03-16 16:42 ` Mauricio Faria de Oliveira [this message]
2018-03-28 14:13 ` [v3, " Michael Ellerman
2018-03-14 22:40 ` [PATCH v3 2/5] rfi-flush: Make it possible to call setup_rfi_flush() again Mauricio Faria de Oliveira
2018-03-14 22:40 ` [PATCH v3 3/5] rfi-flush: Always enable fallback flush on pseries Mauricio Faria de Oliveira
2018-03-14 22:40 ` [PATCH v3 4/5] rfi-flush: Differentiate enabled and patched flush types Mauricio Faria de Oliveira
2018-03-14 22:40 ` [PATCH v3 5/5] rfi-flush: Call setup_rfi_flush() after LPM migration Mauricio Faria de Oliveira
2018-03-14 22:40 ` [TESTS] Create 'enabled_flush_types' boot option, and short-circuit LPM Mauricio Faria de Oliveira
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=bd359480-5b04-91d5-2a9e-9129c6772c41@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
--cc=muriloo@linux.vnet.ibm.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).