Hello,
2013/1/25 Alex Vedenev <
firs...@gmail.com>:
> Can you answer the following questions for your YanaKernel project:
Thank you for being interested in YanaKernel0.
About YanaKernel0, there is not English documentation, but the
following links may help understanding.
http://groups.google.com/group/minix3/browse_thread/thread/d594f52caa8e156
http://groups.google.com/group/minix3/browse_thread/thread/d8b8f7ac975143af
http://groups.google.com/group/minix3/browse_thread/thread/b37eb23f02b65bb0
> What are the goals in your project? What is it for?
Because I am interested in hardware software interface, I spend time
on YanaKernel0.
I implemented YanaKernel0A in C language (and assembly language).
I want to implement YanaKernel0 by hardware, but not yet.
And I want to use task which was implemented by hardware.
There are not the goals, but I spend time on the following processors recently.
+ high level synthesis processor
For example, it is approach to implement processor which embedded
YanaKernel0 in SystemC language.
However, I could not find appropriate high level synthesis tool.
+ low level synthesis processor which can write microcode (or add instruction)
For example, it is approach to implement YanaKernel0 in processor
specific language.
However, I could not find appropriate low level synthesis processor.
> What are the
> differences with existing solutions?
I have not researched existing solutions.
Keywords of YanaKernel0 are simple, resource limited, and hardware
implementable.
About hardware implementable kernel, if kernel can access the
following memories, I want to use kernel which does not access
external memories than kernel which accesses external memories.
+ internal memories which are exceptionless and waitless
+ external memories which are exceptionable and waitable
About YanaKernel0, I separate memories of kernel and memories of
tasks, and inside of kernel accesses only memories of kernel.
Kernel does not support memory management, but task can manage task
which caused exception, and task can support memory management with
exception relating to MMU.
> Why did you choose MINIX 3 for "guest system" in your project?
+ experience
Formerly I patched MINIX-ST, and executed it as user state process of
OS-9/680x0.
+ license
I want to separate license of "guest system" and license of
YanaKernel0 kernel (and processor).
> What is the
> difference of MINIX 3.1.3a and MINIX 3.2.0 for your project?
MINIX with YanaKernel0 is a kind of the demonstrations, and is a kind
of the proofs of concept.
MINIX 3.1.3a uses segmented virtual memory.
MINIX 3.2.0 uses segmented virtual memory and paged virtual memory.
About YanaKernel0, kernel does not support memory management, but task
can support memory management with exception relating to MMU.
About MINIX with YanaKernel0, paged virtual memory influenced MINIX
kernel which is executed as YanaKernel0 task, but did not influence
YanaKernel0 kernel.
Thanks,
Yana