Hi all,
In fact, I am looking for a micro-kernel based hypervisor (like L4:pistachio or
Fiasco) to run on the SCC. The only pointer I found was a port of Fiasco OS for
Intel SCC recently
(http://os.inf.tu-dresden.de/papers_ps/partheymueller-beleg.pdf) and would like
to try this.
I had a few
Dear all,
I am trying to run L4linux on top of fiasco/L4re using an older version from
the svn (for those interested, I am trying to run this on Intel SCC and
therefore need an old build). I am first trying to run this on qemu and can
get the entire linux to boot and display a shell prompt.
Dear all,
I am trying to run L4linux on fiasco/l4re but with the keyboard and VGA
disabled. I can get all the way to the command prompt (of the shell) in the
initramfs but then, on pressing a key, I get a page fault and I cannot debug
the system anymore using the serial_esc. I suspect it is my
in Qemu. Maybe you ran into a similar problem as described in this
thread:
http://os.inf.tu-dresden.de/pipermail/l4-hackers/2012/thread.html#5165
Best regards,
Martin
Am 27.08.2014 um 15:18 schrieb Masti Ramya Jayaram:
Sorry, a couple of typos in the l4linux.cfg
--vim:set ft=lua:
L4
To: Masti Ramya Jayaram; l4-hackers@os.inf.tu-dresden.de
Subject: Re: Minimal requirements to run L4linux using only a serial console
Hi Masti,
you have all of them already! I did not alter any other file beside the files
you already sent. I inserted them into a fresh
snapshot
(http://l4re.org
From: Masti Ramya Jayaram
Sent: 29 August 2014 12:15
To: Martin Schröder; l4-hackers@os.inf.tu-dresden.de
Subject: RE: Minimal requirements to run L4linux using only a serial console
Hey Martin,
I cleaned up my build and it worked - the mistake was mine. I had
Also, given that the thing works with ACPI on, wouldn't it be better to include
ACPI information in the boot instead of changing the driver? Or is this
impossible?
Best,
Ramya
From: Masti Ramya Jayaram
Sent: 29 August 2014 15:55
To: Martin Schröder
,
Martin
Am 29.08.2014 um 15:58 schrieb Masti Ramya Jayaram:
Also, given that the thing works with ACPI on, wouldn't it be better to
include ACPI information in the boot instead of changing the driver? Or is
this impossible?
Best,
Ramya
From: Masti
am missing
something.
Best regards,
Martin
Am 29.08.2014 um 15:58 schrieb Masti Ramya Jayaram:
Also, given that the thing works with ACPI on, wouldn't it be better to
include ACPI information in the boot instead of changing the driver? Or is
this impossible?
Best,
Ramya
Also with acpi on, it does enter the debugger in qemu.
Best,
Ramya
From: Masti Ramya Jayaram
Sent: 29 August 2014 17:45
To: Martin Schröder; l4-hackers@os.inf.tu-dresden.de
Subject: RE: Minimal requirements to run L4linux using only a serial console
Hey
as input to
l4linux.
Thanks a lot for your help for your help.
Best,
Ramya
From: Masti Ramya Jayaram
Sent: 29 August 2014 17:48
To: Martin Schröder; l4-hackers@os.inf.tu-dresden.de
Subject: RE: Minimal requirements to run L4linux using only a serial
From: Martin Schröder [mschroe...@web.de]
Sent: 29 August 2014 23:23
To: Masti Ramya Jayaram; l4-hackers@os.inf.tu-dresden.de
Subject: Re: Minimal requirements to run L4linux using only a serial console
Hi Ramya,
Tx path of UART is working but the Rx part not due to missing
interrupts
Dear all,
I am using fiasco/l4re to run applications (say hello world) and L4linux. The
module list in the two cases looks like this:
entry hello-cfg
kernel fiasco -serial_esc -freq=533000
roottask moe rom/hello.cfg
module l4re
module ned
module hello.cfg
module hello
entry l4linux
kernel
, 2014 at 14:02:41 +, Masti Ramya Jayaram wrote:
I am using fiasco/l4re to run applications (say hello world) and
L4linux. The module list in the two cases looks like this:
entry hello-cfg
kernel fiasco -serial_esc -freq=533000
roottask moe rom/hello.cfg
module l4re
module ned
module
Dear all,
I am trying to create a new package under l4/pkg. The linking of the package
fails and it has to do with the linker path but I am not sure how to fix it.
Here are the details.
Package structure: (relevant parts)
l4/pkg/test/server/src/main.cc
l4/pkg/test/server/src/folder1/test1.c
Okay, I got around it by simply putting the entire header file inclusion in an
extern C{} . Now it works!
Thanks again for your help,
Ramya
From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Masti
Ramya Jayaram [rma...@inf.ethz.ch
Dear all,
I am running a custom application package on fiasco using a serial line (no
keyboard/screen) and I intermittently get faults caused by printf. I notice
that on disassembling the code around the error that the function is called
writev in ulibc. Has anyone experienced something
01, 2014 at 07:54:02 +, Masti Ramya Jayaram wrote:
Thanks for the suggestion. I have one other constraint: I would like
to keep trusted computing base (or the amount of security critical
code as small as possible).
From what I understand from http://l4re.org/doc/index.html, the
following
Hi all,
I have managed to compile a custom C library (libscc-sec) as part of the l4
packages. Now I would like to use it in the bootstrap package (make a call to a
function in the library). I did the following:
a. Added the library as a requirement in pkg/bootstrap/Control
requires:
-dresden.de]
Sent: 02 September 2014 00:00
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Fault in function writev (ulibc)
On Mon Sep 01, 2014 at 16:37:44 +, Masti Ramya Jayaram wrote:
I am running a custom application package on fiasco using a serial
line (no keyboard/screen) and I
-dresden.de] on behalf of Masti
Ramya Jayaram [rma...@inf.ethz.ch]
Sent: 02 September 2014 11:37
To: l4-hackers@os.inf.tu-dresden.de
Subject: Adding a custom library to l4/pkg/bootstrap
Hi all,
I have managed to compile a custom C library (libscc-sec) as part of the l4
packages. Now I would like
(there is
more than what is compiled by module.list I can see)?
Thanks,
ramya
From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Masti
Ramya Jayaram [rma...@inf.ethz.ch]
Sent: 02 September 2014 09:57
To: Adam Lackorzynski; l4-hackers
...@os.inf.tu-dresden.de] on behalf of Jan
Bierbaum [jan.bierb...@os.inf.tu-dresden.de]
Sent: 02 September 2014 21:56
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Adding a custom library to l4/pkg/bootstrap
On 02.09.2014 13:32, Masti Ramya Jayaram wrote:
However, now I am trying to call a function
executables before running them in L4re/fiasco
On Tue Sep 02, 2014 at 14:08:03 +, Masti Ramya Jayaram wrote:
Also, could you elaborate a bit on how one could have smaller
components? I decided to do it at bootstrap at the moment because I
realized that using the IO server also means including
@os.inf.tu-dresden.de
Subject: Re: Adding a custom library to l4/pkg/bootstrap
On 09/03/2014 09:51 AM, Masti Ramya Jayaram wrote:
Hey Jan,
Sorry for underspecifying it. Here are the details.
I have a library called scc-sec under the l4/pkg directory. It has one file:
a. init.c that contains
void
││ │
│ ││ │
│ ││ │
│ ││ │
│ ││ │
│ ││ │
│ ││
On Wed Sep 03, 2014 at 14:43:59 +, Masti Ramya Jayaram wrote:
You mean binaries that are started
Dear all,
I get an error during L4linux boot when I enter the debugger (using ESC) and
resume:
Aborted L4linux due to CLI/STI at 0x534911.
When I disassemble this using gdb:
(gdb) disassemble 0x534911
Dump of assembler code for function cmpxchg8b_emu:
0x00534910 +0: pushf
I forgot to mention that it also does not support the traditional cmpxchg
instructions using the lock line. That is why I disabled it.
Sorry about the multiple emails,
Ramya
Sent from my phone
On 05 Sep 2014, at 18:16, Masti Ramya Jayaram rma...@inf.ethz.ch wrote:
Dear all,
I get
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Checking executables before running them in L4re/fiasco
Hi,
On Fri Sep 05, 2014 at 12:29:15 +, Masti Ramya Jayaram wrote:
Thanks for the information. I have two issues/questions:
a. I looked at the move_modules (which does not do much in my
, Masti Ramya Jayaram wrote:
I forgot to mention that it also does not support the traditional
cmpxchg instructions using the lock line. That is why I disabled it.
That's ok as long it's also ok for native Linux.
On 05 Sep 2014, at 18:16, Masti Ramya Jayaram rma...@inf.ethz.ch wrote:
Dear all
Hi all,
I start l4linux by specifying 64M on memory in its configuration file. I would
like this memory to be a fixed range of physical memory and I was wondering if
there is a way to do it.
I understand from my earlier posts that the image of l4linux is in the same
location everytime
-boun...@os.inf.tu-dresden.de] on behalf of Martin
Schröder [martin.schroe...@openlimit.com]
Sent: 09 September 2014 11:56
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Physical memory allocation to L4linux
Hi Ramya,
Am 09.09.2014 um 11:39 schrieb Masti Ramya Jayaram:
Hi all,
I start l4linux
Dear all,
I would like to prevent access to a part of the address space from sigma0 for
security reasons on my board. For example, I would like to prevent even sigma
from accessing say 0xc000 - 0x of memory. What is the best way to
accomplish this and test it?
Thanks,
ramya
-dresden.de] on behalf of Adam
Lackorzynski [a...@os.inf.tu-dresden.de]
Sent: 09 September 2014 23:16
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Physical memory allocation to L4linux
On Tue Sep 09, 2014 at 16:03:11 +, Masti Ramya Jayaram wrote:
I would like to explain my situation
, 2014 at 07:10:00 +, Masti Ramya Jayaram wrote:
That's ok as long it's also ok for native Linux.
I am not sure what they did with native Linux but I know from the SCC
forums that these instructions do not exist. So I guess that is ok.
I'm wondering how did you end up with the code
only work on memory. The region I want to
protect is not RAM.
b. Given that the setup of sigma0's memory happens in
kernel/fiasco/src/kern/kernel_thread-std.cpp, is there more to be done here?
Thanks.
Ramya
From: Masti Ramya Jayaram
Sent: 10 September
From: Masti Ramya Jayaram
Sent: 10 September 2014 16:07
To: Adam Lackorzynski; l4-hackers@os.inf.tu-dresden.de
Subject: RE: Physical memory allocation to L4linux
Update: Sorry, I misunderstood a few things in the previous email. The change
was in fiasco and not sigma
--
[0:0;fff]
is there a way for me for example to limit RAM and IOMEM access to other
spaces?
Thanks,
ramya
From: Masti Ramya Jayaram
Sent: 11 September 2014 15:51
To: Adam Lackorzynski; l4-hackers@os.inf.tu-dresden.de
Subject: RE: Physical
2014, at 00:38, Adam Lackorzynski a...@os.inf.tu-dresden.de
wrote:
On Fri Sep 12, 2014 at 16:34:17 +, Masti Ramya Jayaram wrote:
I realized that the best place to modify sigma0's capabilities are
when it is created. I see that this happens in
kernel/fiasco/src/kern/kernel_thread-std.cpp
. So I just assumed I was
looking in the wrong place.
I will try to dig a little more and check.
Sent from my phone
On 15 Sep 2014, at 23:55, Adam Lackorzynski a...@os.inf.tu-dresden.de
wrote:
Hi,
On Mon Sep 15, 2014 at 18:25:37 +, Masti Ramya Jayaram wrote:
Thanks for the input
Dear all,
I would like to extract the minimal subset of uclibc required by bootstrap,
sigma and their dependencies only. My idea is to have these modules use the
smaller libc while retain the usual uclibc build for the other packages.
I intend to go about this by copying uclibc (say into
From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Masti
Ramya Jayaram [rma...@inf.ethz.ch]
Sent: 16 September 2014 17:53
To: l4-hackers@os.inf.tu-dresden.de
Subject: Trimming uclibc in l4
Dear all,
I would like to extract the minimal subset
Hey Markus,
I am using a version from April 2011 but even that version contains a lot of
things that bootstrap and sigma0 do not need. :) Did you mean more recent than
that?
best,
ramya
p.s. my board requires that I run an older version of the kernel - so the pain.
this
package (and adapting l4/mk) might be easier than stripping things down
yourself.
Bjoern
Am 16.09.2014 um 19:02 schrieb Masti Ramya Jayaram:
Update: turns out it is not very simple to compile just bootstrap against a
smaller library because the l4/mk/modes.inc file defaults to the uclibc
library
Dear all,
I see that in the default l4linux configuration, it uses ned, moe to start up.
However, I am not sure about the run-time interaction between them. More
specifically,
a. Does l4linux need them during its run-time? For example, does l4linux go
directly to sigma0 for memory or does it
Dear all,
I would like to perform some cleanup operations after l4linux shuts down..such
as zero out all the memory it used and re-encrypt the original vmlinux image. I
would like to know how I could do this from sigma0 preferably or even in the
fiasco kernel. Could anyone point me to where
46 matches
Mail list logo