From: Richard Weinberger <richard@nod.at>
To: Joel Fernandes <agnel.joel@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] UML hangs with hrtimer test module
Date: Thu, 29 Mar 2018 22:34:46 +0200 [thread overview]
Message-ID: <5210954.RitFgLWNVY@blindfold> (raw)
In-Reply-To: <CAD=GYpbAfqdEquXWdvHwrxaPQwi8Dyh=j9+6=SpwZ3zqnKSq0Q@mail.gmail.com>
Am Donnerstag, 29. März 2018, 22:20:47 CEST schrieb Joel Fernandes:
> Thanks a lot! I am wondering why the same compiler works when running
> the test for a regular image. Maybe different compiler flags. Anyway
> good to learn this.
>
> Also one more slightly OT question, why is UML only doing UP ? Is it
> extremely hard to do SMP for UML?
Long story short, nobody implemented SMP so far. :-)
Because SKAS3/0 we had a SMP implementation of TT mode.
In terms of UML implementing SMP means having multiple threads
that handle the userspace loop in arch/um/os-Linux/skas/process.c.
We could also do a poor man's SMP implementation first, where only user
processes run in parallel.
IOW userspace() in arch/um/os-Linux/skas/process.c is still a single thread
but it let's run up to N user space thread and only if the call into the
kernel we degrade to UP.
Adding SMP is not extremely hard but it requires a lot of re-work of the UML
core and introduces tons of new issues.
That said, volunteers are welcome!
Thanks,
//richard
prev parent reply other threads:[~2018-03-29 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 10:28 [uml-devel] UML hangs with hrtimer test module Joel Fernandes
2018-03-28 11:04 ` Richard Weinberger
2018-03-28 13:11 ` Geert Uytterhoeven
2018-03-28 13:19 ` Richard Weinberger
2018-03-28 22:19 ` Joel Fernandes
2018-03-28 22:35 ` Richard Weinberger
2018-03-29 6:04 ` Geert Uytterhoeven
2018-03-29 20:20 ` Joel Fernandes
2018-03-29 20:34 ` Richard Weinberger [this message]
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=5210954.RitFgLWNVY@blindfold \
--to=richard@nod.at \
--cc=agnel.joel@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@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.