All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Natale Patriciello <natale.patriciello@gmail.com>
Cc: user-mode-linux-user@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: UML not maintained anymore?
Date: Fri, 17 Mar 2017 16:46:43 +0100	[thread overview]
Message-ID: <20170317154643.GE4771@amd> (raw)
In-Reply-To: <20170228152811.vwn5koz3jhweeo7o@judith.localdomain>

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

On Tue 2017-02-28 16:28:11, Natale Patriciello wrote:
> It seems there is no interest in fixing bugs (such as [1]). Moreover,
> same guest filesystem (same host os, distribution, etc.) on two
> different machines (i7-2630 the first, i7-7700HQ the second) yield
> different results, with crashes and corruption of filesystem in the
> modern computer.  So, can I consider UML as a legacy thing in the Linux
> kernel? With what I can replace it (I'm doing TCP research, and I focus
> on the networking stack)?

Well.. if it worked before and does not work now, that's a regression
and will be fixed. Bisect would be useful.

If it never worked on new CPUs, that's different situation...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-03-17 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 15:28 UML not maintained anymore? Natale Patriciello
2017-03-17 15:46 ` Pavel Machek [this message]
2017-03-17 16:55   ` Richard Weinberger

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=20170317154643.GE4771@amd \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natale.patriciello@gmail.com \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.