From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) by kanga.kvack.org (Postfix) with ESMTP id EAC028E0008 for ; Wed, 19 Dec 2018 17:50:20 -0500 (EST) Received: by mail-lj1-f200.google.com with SMTP id l12-v6so5897769ljb.11 for ; Wed, 19 Dec 2018 14:50:20 -0800 (PST) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id e11-v6sor12267462ljg.24.2018.12.19.14.50.18 for (Google Transport Security); Wed, 19 Dec 2018 14:50:18 -0800 (PST) Subject: Re: [PATCH 2/6] __wr_after_init: write rare for static allocation References: <20181204121805.4621-1-igor.stoppa@huawei.com> <20181204121805.4621-3-igor.stoppa@huawei.com> <20181212104900.0af52c34@mschwideX1> From: Igor Stoppa Message-ID: Date: Thu, 20 Dec 2018 00:50:12 +0200 MIME-Version: 1.0 In-Reply-To: <20181212104900.0af52c34@mschwideX1> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Martin Schwidefsky , Andy Lutomirski Cc: linux-arch , linux-s390 , Heiko Carstens , Benjamin Herrenschmidt , Kees Cook , Matthew Wilcox , Igor Stoppa , Nadav Amit , Peter Zijlstra , Dave Hansen , linux-integrity , Kernel Hardening , Linux-MM , LKML On 12/12/2018 11:49, Martin Schwidefsky wrote: > On Wed, 5 Dec 2018 15:13:56 -0800 > Andy Lutomirski wrote: >> Hi s390 and powerpc people: it would be nice if this generic >> implementation *worked* on your architectures and that it will allow >> you to add some straightforward way to add a better arch-specific >> implementation if you think that would be better. > > As the code is right now I can guarantee that it will not work on s390. OK, I have thrown the towel wrt developing at the same time for multiple architectures. ATM I'm oriented toward getting support for one (x86_64), leaving the actual mechanism as architecture specific. Then I can add another one or two and see what makes sense to refactor. This approach should minimize the churning, overall. -- igor