linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Laurent Vivier <laurent@vivier.eu>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-m68k <linux-m68k@lists.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: Thu, 30 Sep 2021 23:14:50 +0200	[thread overview]
Message-ID: <506fe100-04b6-e465-f4b8-bae58ab505ac@physik.fu-berlin.de> (raw)
In-Reply-To: <90ab81cd-0d83-9537-b7d8-40e4bffa152e@vivier.eu>

Hi!

On 9/30/21 23:11, Laurent Vivier wrote:
>>> --- a/arch/m68k/Kconfig.machine
>>> +++ b/arch/m68k/Kconfig.machine
>>> @@ -145,6 +145,23 @@ config SUN3
>>>
>>>           If you don't want to compile a kernel exclusively for a Sun 3, say N.
>>>
>>> +config VIRT
>>> +       bool "Virtual M68k Machine support"
>>> +       depends on MMU
>>> +       select MMU_MOTOROLA if MMU
>>> +       select M68040
>>> +       select LEGACY_TIMER_TICK
>>
>> Can we avoid selecting this for a new platform?
>>
> 
> I tried but I was not able to have a working scheduler.
> 
> As the machine has been tested with this option and most of the other m68k machines uses it, I will
> keep it.

FWIW, the VM in its current form works very well and reliable and has been
in use as a Debian porterbox for almost a year now without any issues.

root@mitchy:~# uname -a
Linux mitchy 5.10.0-rc1-183617-gd7f4e16357f6 #1 Mon Nov 2 12:06:55 CET 2020 m68k GNU/Linux
root@mitchy:~# uptime
 23:13:47 up 332 days, 10:04,  1 user,  load average: 0.08, 0.05, 0.06
root@mitchy:~#

Would be great if we could get this feature added upstream so I can enable
this kernel configuration in Debian.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


  reply	other threads:[~2021-09-30 21:14 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
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 [this message]
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=506fe100-04b6-e465-f4b8-bae58ab505ac@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=geert@linux-m68k.org \
    --cc=laurent@vivier.eu \
    --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).