From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/3] rfi-flush: Make it possible to call setup_rfi_flush() again
Date: Tue, 13 Mar 2018 15:13:11 -0300 [thread overview]
Message-ID: <db75ecdd-32da-d429-8ea6-3bd1453bd89e@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180313185916.3e4a0ea6@kitsune.suse.cz>
On 03/13/2018 02:59 PM, Michal Suchánek wrote:
> Maybe it would make more sense to move the messages to the function
> that actually patches in the instructions?
That helps, but if the instructions are not patched (e.g., no_rfi_flush)
then there is no information about what the system actually supports,
which is useful for diagnostics/debugging (and patch verification! :-) )
cheers,
mauricio
next prev parent reply other threads:[~2018-03-13 18:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 21:33 [PATCH 0/3] Setup RFI flush after PowerVM LPM migration Mauricio Faria de Oliveira
2018-02-14 21:33 ` [PATCH 1/3] rfi-flush: Move the logic to avoid a redo into the debugfs code Mauricio Faria de Oliveira
2018-02-14 21:33 ` [PATCH 2/3] rfi-flush: Make it possible to call setup_rfi_flush() again Mauricio Faria de Oliveira
2018-02-15 7:13 ` Michal Suchánek
2018-02-16 11:50 ` Mauricio Faria de Oliveira
2018-02-20 9:59 ` Michael Ellerman
2018-02-20 17:06 ` Michal Suchánek
2018-03-05 22:46 ` Mauricio Faria de Oliveira
2018-03-06 10:21 ` Michal Suchánek
2018-03-06 12:15 ` Michael Ellerman
2018-03-06 12:55 ` Michal Suchánek
2018-03-12 23:08 ` Mauricio Faria de Oliveira
2018-03-13 11:39 ` Michael Ellerman
2018-03-13 12:14 ` Mauricio Faria de Oliveira
2018-03-13 17:59 ` Michal Suchánek
2018-03-13 18:13 ` Mauricio Faria de Oliveira [this message]
2018-03-13 18:36 ` Michal Suchánek
2018-03-13 20:18 ` Mauricio Faria de Oliveira
2018-03-16 14:18 ` Michael Ellerman
2018-03-16 16:51 ` Mauricio Faria de Oliveira
2018-02-14 21:33 ` [PATCH 3/3] rfi-flush: Call setup_rfi_flush() after LPM migration Mauricio Faria de Oliveira
2018-02-14 21:39 ` [PATCH] DEBUG: shortcut mobility fixup/migration store, and abuse no_rfi_flush 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=db75ecdd-32da-d429-8ea6-3bd1453bd89e@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
/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).