From: Laurent Vivier <laurent@vivier.eu>
To: linux-kernel@vger.kernel.org
Cc: linux-m68k@lists.linux-m68k.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-rtc@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH 2/2] m68k: introduce a virtual m68k machine
Date: Tue, 27 Apr 2021 19:20:01 +0200 [thread overview]
Message-ID: <a9c75ae7-6023-6b6c-260f-a0d6841ea4fa@vivier.eu> (raw)
In-Reply-To: <20210323221430.3735147-3-laurent@vivier.eu>
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@vivier.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
next prev parent reply other threads:[~2021-04-27 17:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 22:14 [PATCH 0/2] m68k: Add Virtual M68k Machine Laurent Vivier
2021-03-23 22:14 ` [PATCH 1/2] rtc: goldfish: remove dependency to OF Laurent Vivier
2021-03-23 22:14 ` [PATCH 2/2] m68k: introduce a virtual m68k machine Laurent Vivier
2021-04-27 17:20 ` Laurent Vivier [this message]
2021-04-28 12:07 ` Geert Uytterhoeven
2021-04-28 12:15 ` Laurent Vivier
2021-09-30 20:56 ` John Paul Adrian Glaubitz
2021-09-30 21:01 ` Laurent Vivier
2021-10-01 1:08 ` Finn Thain
2021-04-28 12:04 ` Geert Uytterhoeven
2021-04-28 23:06 ` Josh Juran
2021-04-29 7:23 ` Geert Uytterhoeven
2021-09-30 21:11 ` Laurent Vivier
2021-09-30 21:14 ` John Paul Adrian Glaubitz
2021-04-16 20:26 ` [PATCH 0/2] m68k: Add Virtual M68k Machine Alexandre Belloni
2021-04-16 20:34 ` Alexandre Belloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a9c75ae7-6023-6b6c-260f-a0d6841ea4fa@vivier.eu \
--to=laurent@vivier.eu \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-rtc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).