From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967894AbcA1A7N (ORCPT ); Wed, 27 Jan 2016 19:59:13 -0500 Received: from mailapp01.imgtec.com ([195.59.15.196]:24540 "EHLO mailapp01.imgtec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966103AbcA1A6r (ORCPT ); Wed, 27 Jan 2016 19:58:47 -0500 Message-ID: <56A967BF.70200@imgtec.com> Date: Wed, 27 Jan 2016 16:58:39 -0800 From: Leonid Yegoshin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: "Maciej W. Rozycki" CC: , Will Deacon , "Peter Zijlstra" , "Michael S. Tsirkin" , , Arnd Bergmann , , Andrew Cooper , Russell King - ARM Linux , , Stefano Stabellini , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Joe Perches , David Miller , , , , , , , , , , , , , , "Ralf Baechle" , Ingo Molnar , , , Michael Ellerman Subject: Re: [v3,11/41] mips: reuse asm-generic/barrier.h References: <20160113104516.GE25458@arm.com> <5696CF08.8080700@imgtec.com> <20160114121449.GC15828@arm.com> <5697F6D2.60409@imgtec.com> <20160114203430.GC3818@linux.vnet.ibm.com> <56980C91.1010403@imgtec.com> <20160114212913.GF3818@linux.vnet.ibm.com> <569814F2.50801@imgtec.com> <20160114225510.GJ3818@linux.vnet.ibm.com> <56983054.4070807@imgtec.com> <20160115004753.GN3818@linux.vnet.ibm.com> <56984642.3090106@imgtec.com> In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.20.3.92] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/27/2016 03:26 AM, Maciej W. Rozycki wrote: > On Fri, 15 Jan 2016, Leonid Yegoshin wrote: > >>> So you need to build a different kernel for some types of MIPS systems? >>> Or do you do boot-time rewriting, like a number of other arches do? >> I don't know. I would like to have responses. Ralf asked Maciej about old >> systems and that came nowhere. Even rewrite - don't know what to do with that: >> no lightweight SYNC or no SYNC at all - yes, it is still possible that SYNC on >> some systems can be too heavy or even harmful, nobody tested that. > I don't recall being asked; mind that I might not get to messages I have > not been cc-ed in a timely manner and I may miss some altogether. With > the amount of mailing list traffic that passes by me my scanner may fail > to trigger. Sorry if this causes anybody trouble, but such is life. > > Coincidentally, I have just posted some notes on SYNC in a different > thread, see . > There's a reference to an older message of mine there too. I hope this > answers your questions. > > Maciej In http://patchwork.linux-mips.org/patch/10505/the very last mesg exchange is: Maciej, do you have an R4000 / R4600 / R5000 / R7000 / SiByte system at hand to test this? ... Ralf Maciej W. Rozycki- June 5, 2015, 9:18 p.m. On Fri, 5 Jun 2015, Ralf Baechle wrote: > do you have an R4000 / R4600 / R5000 / R7000 / SiByte system at hand to > test this? I should be able to check R4400 (that is virtually the same as R4000) next week or so. As to SiByte -- not before next month I'm afraid. I don't have access to any of the other processors you named. You may want to find a better person if you want to accept this change soon. Maciej ... and that stops forever... - Leonid.