Hey Adam,
Yes I can confirm that I was a able to trace the code from fpage_map() to map()
but I see zero addresses there - i.e. When I check the receiver and sender
addresses and size everything is zero. This was despite it being correct until
the handle_sigma0_request() function in
Hey Adam,
Thanks for the input. I will try changing one of the suggested functions.
It would be great out of curiosity if you could elucidate why the following
occurs.
I see that there is a new iomem region being created and this happens only when
I try to read from the mapped region - not
Hi,
On Mon Sep 15, 2014 at 18:25:37 +, Masti Ramya Jayaram wrote:
Thanks for the input. I will try changing one of the suggested functions.
It would be great out of curiosity if you could elucidate why the following
occurs.
I see that there is a new iomem region being created and
On Wed Sep 10, 2014 at 07:46:20 +, Masti Ramya Jayaram wrote:
thanks a lot for the replies. I still have a few questions/clarifications
though. :-)
a. Is there a way to implement the MODE=sigma for linux? I could not find
anything that points to it.
That could be done but would
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 in the init_workload()
function. I do not exactly understand how
,
Ramya
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
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
-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 09:46
To: Adam Lackorzynski; l4-hackers@os.inf.tu-dresden.de
Subject: RE: Physical memory allocation to L4linux
Hey Adam,
thanks a lot for the replies. I still have a few questions/clarifications
though. :-)
a. Is there a way to implement the MODE=sigma for linux? I could not find
anything
Hi Ramya,
Am 09.09.2014 um 11:39 schrieb Masti Ramya Jayaram:
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.
MYRAM = new Device() {
.hid=
-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
On Tue Sep 09, 2014 at 16:03:11 +, Masti Ramya Jayaram wrote:
I would like to explain my situation better. Here is what I intend:
a. What is the lowest module (bootstrap, fiasco, sigma, moe,
ned,l4linux) that can be confined not access a portion of the address
space?
Without changing
12 matches
Mail list logo
