From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4012z26Fw4zF0Tn for ; Wed, 14 Mar 2018 05:13:18 +1100 (AEDT) Received: from pps.filterd (m0098417.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w2DIBc6s096958 for ; Tue, 13 Mar 2018 14:13:16 -0400 Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by mx0a-001b2d01.pphosted.com with ESMTP id 2gpj5cm4xa-1 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NOT) for ; Tue, 13 Mar 2018 14:13:15 -0400 Received: from localhost by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 13 Mar 2018 12:13:15 -0600 Subject: Re: [PATCH 2/3] rfi-flush: Make it possible to call setup_rfi_flush() again To: =?UTF-8?Q?Michal_Such=c3=a1nek?= Cc: linuxppc-dev@lists.ozlabs.org References: <1518644021-17037-1-git-send-email-mauricfo@linux.vnet.ibm.com> <1518644021-17037-3-git-send-email-mauricfo@linux.vnet.ibm.com> <20180215081358.2f37cda4@naga.suse.cz> <87lgforngp.fsf@concordia.ellerman.id.au> <20180220180621.11265945@kitsune.suse.cz> <2bb5a110-3ea4-af5c-81fb-cf5350587dff@linux.vnet.ibm.com> <876069flhq.fsf@concordia.ellerman.id.au> <20180306135522.040707de@kitsune.suse.cz> <876060gq5s.fsf@concordia.ellerman.id.au> <20180313185916.3e4a0ea6@kitsune.suse.cz> From: Mauricio Faria de Oliveira Date: Tue, 13 Mar 2018 15:13:11 -0300 MIME-Version: 1.0 In-Reply-To: <20180313185916.3e4a0ea6@kitsune.suse.cz> Content-Type: text/plain; charset=utf-8; format=flowed Message-Id: List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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