From: Richard Weinberger <richard@nod.at>
To: Rob Landley <rob@landley.net>,
Anton Ivanov <anton.ivanov@kot-begemot.co.uk>,
Al Viro <viro@zeniv.linux.org.uk>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Fwd: Mail delivery failed: returning message to sender
Date: Tue, 23 Sep 2014 17:13:06 +0200 [thread overview]
Message-ID: <54218E02.10506@nod.at> (raw)
In-Reply-To: <54218A8B.5030808@landley.net>
Rob,
Am 23.09.2014 16:58, schrieb Rob Landley:
> As long as somebody's paying attention to UML again: what would be
> involved in adding support for arm/mips/sh4/sparc...
>
> I've mostly wandered off to use qemu these days, and I package system
> images with native compilers you can boot up and compile software in:
>
> http://landley.net/aboriginal/bin/
>
> (Grab a system-image-$ARCH.tar.bz2 and ./run-emulator.sh in that, or
> ./dev-environment.sh if you want it to truncate and ext2 format a
> scratch space block device and and mount it on /home in the emulated
> system so you have persistent storage.)
>
> I'm under the impression that user mode linux would need some glue code
> to run on powerpc, but dunno what it would actually be...
Supporting non-x86 archs needs more than just some glue code.
First the target arch would need support for changing syscall numbers with ptrace(),
or even better PTRACE_SYSEMU support. UML also depends on mcontext of SIGSEGV to
get the faulting address.
On ARM for example VIVT caches could be a problem too.
Al has all the glory details...
Thanks,
//richard
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2014-09-23 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XW6rt-0005E0-Pl@sog-mx-2.v43.ch3.sourceforge.com>
2014-09-22 18:39 ` [uml-devel] Fwd: Mail delivery failed: returning message to sender Anton Ivanov
2014-09-23 14:58 ` Rob Landley
2014-09-23 15:13 ` Richard Weinberger [this message]
2014-09-23 15:40 ` Anton Ivanov
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=54218E02.10506@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@kot-begemot.co.uk \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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.