From: Stas Sergeev <stsp@list.ru>
To: Andrew Bird <ajb@spheresystems.co.uk>, linux-msdos@vger.kernel.org
Subject: Re: Ubuntu 16.04 on i386 has VM86 disabled again
Date: Mon, 25 Apr 2016 15:52:13 +0300 [thread overview]
Message-ID: <571E12FD.8070607@list.ru> (raw)
In-Reply-To: <20160425131651.d76bec4ef1f6394e2452d23b@spheresystems.co.uk>
25.04.2016 15:16, Andrew Bird пишет:
> Hi all,
> Just a quick note to let people know that if you upgrade your i386 Ubuntu to 16.04 LTS release, you'll find that you are only using cpu emulation again. I naively thought that fixing the problem for Wily HWE kernel would automatically mean that Xenial would come out with the fix. If this slow operation affects you, and you'd like it fixed, please visit the launchpad bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574602 and indicate that it affects you and its importance.
That was the "right" thing to do. Or at least justified and discussed.
If we want vm86(), we need to re-implement it properly.
I have a word from top linux devs (including Linus himself)
that properly implemented vm86() will stay enabled.
Or the one can use kvm, which can already be enabled
in dosemu config.
Currently there are no resources for either re-implementing
vm86() or fixing kvm support to the state when it can be
enabled by default. But feel free to contribute. :)
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-25 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 12:16 Ubuntu 16.04 on i386 has VM86 disabled again Andrew Bird
2016-04-25 12:52 ` Stas Sergeev [this message]
2016-04-26 9:17 ` Paul Crawford
2016-04-26 10:09 ` Andrew Bird
2016-04-26 10:59 ` Stas Sergeev
2016-06-11 8:40 ` Andrew Bird
2016-04-26 10:43 ` Stas Sergeev
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=571E12FD.8070607@list.ru \
--to=stsp@list.ru \
--cc=ajb@spheresystems.co.uk \
--cc=linux-msdos@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