lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <02a27887-55ce-2101-efce-b1236e164f15@csgroup.eu>
Date:   Wed, 25 Nov 2020 07:36:49 +0100
From:   Christophe Leroy <christophe.leroy@...roup.eu>
To:     Michael Ellerman <mpe@...erman.id.au>,
        Arnd Bergmann <arnd@...db.de>
Cc:     Kate Stewart <kstewart@...uxfoundation.org>,
        Mark Rutland <mark.rutland@....com>,
        "Desnes A. Nunes do Rosario" <desnesn@...ux.ibm.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        ALSA Development Mailing List <alsa-devel@...a-project.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        Jaroslav Kysela <perex@...ex.cz>,
        Richard Fontana <rfontana@...hat.com>,
        Paul Mackerras <paulus@...ba.org>,
        Miquel Raynal <miquel.raynal@...tlin.com>,
        Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
        Fabio Estevam <festevam@...il.com>,
        Sasha Levin <sashal@...nel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Jonathan Corbet <corbet@....net>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Takashi Iwai <tiwai@...e.com>,
        YueHaibing <yuehaibing@...wei.com>,
        Michal Simek <michal.simek@...inx.com>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Leonardo Bras <leonardo@...ux.ibm.com>,
        DTML <devicetree@...r.kernel.org>,
        Andrew Donnellan <ajd@...ux.ibm.com>,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
        Marc Zyngier <marc.zyngier@....com>,
        Alistair Popple <alistair@...ple.id.au>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
        Nicholas Piggin <npiggin@...il.com>,
        Alexios Zavras <alexios.zavras@...el.com>,
        Mark Brown <broonie@...nel.org>, git@...inx.com,
        Linux Fbdev development list <linux-fbdev@...r.kernel.org>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Allison Randal <allison@...utok.net>,
        Christophe Leroy <christophe.leroy@....fr>,
        Michal Simek <monstr@...str.eu>, Wei Hu <weh@...rosoft.com>,
        Christian Lamparter <chunkeey@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Armijn Hemel <armijn@...ldur.nl>,
        Rob Herring <robh+dt@...nel.org>,
        Enrico Weigelt <info@...ux.net>,
        "David S. Miller" <davem@...emloft.net>,
        Thiago Jung Bauermann <bauerman@...ux.ibm.com>
Subject: Re: [PATCH 0/2] powerpc: Remove support for ppc405/440 Xilinx
 platforms



Le 21/05/2020 à 12:38, Christophe Leroy a écrit :
> 
> 
> Le 21/05/2020 à 09:02, Michael Ellerman a écrit :
>> Arnd Bergmann <arnd@...db.de> writes:
>>> +On Wed, Apr 8, 2020 at 2:04 PM Michael Ellerman <mpe@...erman.id.au> wrote:
>>>> Benjamin Herrenschmidt <benh@...nel.crashing.org> writes:
>>>>> On Fri, 2020-04-03 at 15:59 +1100, Michael Ellerman wrote:
>>>>>> Benjamin Herrenschmidt <benh@...nel.crashing.org> writes:
>>>>> IBM still put 40x cores inside POWER chips no ?
>>>>
>>>> Oh yeah that's true. I guess most folks don't know that, or that they
>>>> run RHEL on them.
>>>
>>> Is there a reason for not having those dts files in mainline then?
>>> If nothing else, it would document what machines are still being
>>> used with future kernels.
>>
>> Sorry that part was a joke :D  Those chips don't run Linux.
>>
> 
> Nice to know :)
> 
> What's the plan then, do we still want to keep 40x in the kernel ?
> 
> If yes, is it ok to drop the oldies anyway as done in my series 
> https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=172630 ?
> 
> (Note that this series will conflict with my series on hugepages on 8xx due to the 
> PTE_ATOMIC_UPDATES stuff. I can rebase the 40x modernisation series on top of the 8xx hugepages 
> series if it is worth it)
> 

Do we still want to keep 40x in the kernel ? We don't even have a running 40x QEMU machine as far as 
I know.

I'm asking because I'd like to drop the non CONFIG_VMAP_STACK code to simplify and ease stuff (code 
that works with vmalloc'ed stacks also works with stacks in linear memory), but I can't do it 
because 40x doesn't have VMAP_STACK and should I implement it for 40x, I have to means to test it.

So it would ease things if we could drop 40x completely, unless someone there has a 40x platform to 
test stuff.

Thanks
Christophe

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ