linux-kernel - Re: [PATCH 2/2] m68k: introduce a virtual m68k machine

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a9c75ae7-6023-6b6c-260f-a0d6841ea4fa@vivier.eu>
Date:   Tue, 27 Apr 2021 19:20:01 +0200
From:   Laurent Vivier <laurent@...ier.eu>
To:     linux-kernel@...r.kernel.org
Cc:     linux-m68k@...ts.linux-m68k.org,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        linux-rtc@...r.kernel.org, Alessandro Zummo <a.zummo@...ertech.it>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>
Subject: Re: [PATCH 2/2] m68k: introduce a virtual m68k machine

Hi,

Le 23/03/2021 à 23:14, Laurent Vivier a écrit :
> This machine allows to have up to 3.2 GiB and 128 Virtio devices.
> 
> It is based on android goldfish devices.
> 
> Signed-off-by: Laurent Vivier <laurent@...ier.eu>
> ---
>  arch/m68k/Kbuild                           |   1 +
>  arch/m68k/Kconfig.machine                  |  17 +++
>  arch/m68k/configs/virt_defconfig           |  93 ++++++++++++++++
>  arch/m68k/include/asm/irq.h                |   3 +-
>  arch/m68k/include/asm/pgtable_mm.h         |   7 ++
>  arch/m68k/include/asm/setup.h              |  44 ++++++--
>  arch/m68k/include/asm/virt.h               |  26 +++++
>  arch/m68k/include/uapi/asm/bootinfo-virt.h |  18 ++++
>  arch/m68k/include/uapi/asm/bootinfo.h      |   1 +
>  arch/m68k/kernel/Makefile                  |   1 +
>  arch/m68k/kernel/head.S                    |  30 ++++++
>  arch/m68k/kernel/setup_mm.c                |   9 ++
>  arch/m68k/mm/kmap.c                        |  20 ++--
>  arch/m68k/virt/Makefile                    |   6 ++
>  arch/m68k/virt/config.c                    | 118 +++++++++++++++++++++
>  arch/m68k/virt/ints.c                      | 110 +++++++++++++++++++
>  arch/m68k/virt/platform.c                  |  80 ++++++++++++++
>  arch/m68k/virt/timer.c                     |  91 ++++++++++++++++
>  18 files changed, 658 insertions(+), 17 deletions(-)
>  create mode 100644 arch/m68k/configs/virt_defconfig
>  create mode 100644 arch/m68k/include/asm/virt.h
>  create mode 100644 arch/m68k/include/uapi/asm/bootinfo-virt.h
>  create mode 100644 arch/m68k/virt/Makefile
>  create mode 100644 arch/m68k/virt/config.c
>  create mode 100644 arch/m68k/virt/ints.c
>  create mode 100644 arch/m68k/virt/platform.c
>  create mode 100644 arch/m68k/virt/timer.c
> 

As 5.12 has been released, is this possible to consider having this new machine in the next release?

All changes are contained under arch/m68k and protected by the CONFIG_VIRT flag. This should not
have any impact on the other m68k machines. In any case, I'll be able to maintain the machine and
fix any problem.

Thanks,
Laurent