9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] hackathon writeup
Date: Thu, 18 Aug 2022 17:02:35 -0700	[thread overview]
Message-ID: <Yv7TG3YcRMeBsygZ@wopr> (raw)
In-Reply-To: <CABB-WO-QnELdsxzQV8AnpukmEBgH9PMhVVipVQZaEY+bzFYoxg@mail.gmail.com>

On Fri, Aug 19, 2022 at 12:37:04AM +0100, Stuart Morrow wrote:
> And VMX doesn't run on my X301 even though virtualisation
> exists on Core 2 Duo (and is/was enabled in the BIOS).

VMX requires a Westmere or newer Intel processor.  The earliest
generation of Thinkpad X series laptop to support this is the X230, a
machine otherwise roundly inferior to the X301.  Core 2 Duo chips
support the VT-d instructions but not EPT or unrestricted guests.

> And people run 9front on hardware that doesn't have virtualisation
> at all.

With the possible exception of the Ryzen line, hardware too old to
support virtualization is unlikely to run linuxemu at an acceptable
speed.  As for User-Mode Linux, it's single-cpu and doesn't support
anything but x86-based processors either.  (Sure, it works on Itanium
and PowerPC, but 9front doesn't.)  

The syscalls problem isn't that we don't know which ones to implement,
it's that Linux creates and deprecates them at a rate faster than anyone
can keep up with.  I am positive this is the case worldwide, not just
for us -- otherwise, things like Docker on OS X would not virtualize an
entire OS just to make use of Linux containers.  The engineering cost to
virtualize a platform and boot Linux on it is lower than the engineering
cost to keep up with whatever the hell the Linux horde throws at the
kernel this week.

khm

  parent reply	other threads:[~2022-08-19  0:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17  3:27 ori
2022-08-18 22:37 ` Stuart Morrow
2022-08-18 22:52 ` Stuart Morrow
2022-08-18 23:09   ` Stanley Lieber
2022-08-18 23:32     ` Stuart Morrow
2022-08-18 23:11   ` Kurt H Maier
2022-08-18 23:33     ` Stuart Morrow
2022-08-18 23:55       ` Jacob Moody
2022-08-19  0:05         ` ori
2022-10-14  5:45           ` 9p2000.ix (Was Re: [9front] hackathon writeup) unobe
2022-08-19 11:34         ` [9front] hackathon writeup Stuart Morrow
2022-08-19 13:21           ` Jacob Moody
2022-08-18 23:04 ` Stuart Morrow
2022-08-18 23:24   ` ori
2022-08-18 23:37     ` Stuart Morrow
2022-08-18 23:43       ` ori
2022-08-19  0:02       ` Kurt H Maier [this message]
2022-08-19  0:23         ` qwx
2022-08-19  1:54           ` Kurt H Maier
2022-08-19  2:02             ` qwx
2022-08-19  7:08         ` Steve Simon
2022-08-20  1:38           ` Xiao-Yong Jin
2022-08-20  3:57             ` ori
2022-08-19 19:52         ` Thaddeus Woskowiak
2022-08-19 21:13           ` David Arnold
2022-08-19 19:11   ` Aram Hăvărneanu
2022-08-19 20:40     ` Stuart Morrow
2022-08-20 13:14       ` Stuart Morrow
2022-08-22 17:54         ` Aram Hăvărneanu
2022-08-22 17:56           ` Kurt H Maier

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=Yv7TG3YcRMeBsygZ@wopr \
    --to=khm@sciops.net \
    --cc=9front@9front.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).