September 5, 2007

AROS64 - report

Hello there!

It has been a very very long time since I wrote anything last time. I Hope you still visit this site :)

Since I was very busy with my work at Uni, I have abandoned idea of writing new kernel by myself, only. Sure it would be nice to do something like that alone, but I'm afraid I would end up with a half-ready kernel, a patchwork which would be big enough to let exec.library work. Nothing less, nothing more.

The plans have changed. I will make a quicker amd64 port - a slightly modified x86 version for amd64 cpu. The old concept reborn. The huge disadvantage is (yes, you will be disappointed now) that the new kernel will offer almost nothing more than the x86 one. That means - all applications will still run in one huge address space common to all processes. It's still the fastest possible approach on x86_64 architecture - some 2 MiB pages covering the very first 4 GiB address space - all of them in translation look-aside buffer (TLB) of the CPU. The SysBase pointer is still at absolute address 4, but it's use is deprecated. One should access the CPU-local SysBase variable at address %GS:8.

What are the advantages, will you ask? Well, have a look at the screenshot. The core libraries are already there. The scheduler should work, at least in theory :). Many libraries and modules may be already compiled thanks to the enormous effort of Henning Kiel, who fights with badly written sources and let them compile. Once irq.hidd and timer.device are done, I should have AROS working on amd64. Neato, huh? Apart from that, I have avoided assembler code as much as possible. Even interrupt and exception handlers are pure C called by very small context-saving asm stub.

As soon as the x86_64 port of AROS will be ready (and bounty will be satisfied), I will start project aiming at creation of new kernel for our OS. I promise.

Stay tuned. Some interesting news are coming....

Labels:

6 Comments:

Blogger dammy said...

We may have to wait longer for a killer kernel, but atleast AROS64 is moving forward.

Dammy

2:54 AM  
Anonymous iaint said...

Wanting to rewrite the kernel... not enough time... I feel your pain.

Good luck with the "killer kernel"...

12:01 PM  
Blogger chris said...

Good work on the port. To be honest, I was a bit nervous about having two kernels, one with memory protection on one architecture, and one without.

I don't know enough about the subject but I was worried AROS would be forked with new features becoming dependent on the new kernel. It's too small a project for that and it too well suited to older non-64bit machines.

I'd like to see a unified feature set across platforms, even if it takes longer. Let me know if I'm barking up the wrong tree here.

Chris

5:56 PM  
Blogger Graham said...

I agree.

I think the 'killer kernel' should be left for a separate 'AROS-NG' project.
IMHO! :-)
PS - Good to see Michal back on the blog!

2:03 PM  
Blogger Hombre said...

It's too small a project for that and it too well suited to older non-64bit machines.

there is no true 64bit on x86 yeah the amiga os has true 64bit and beyond . All x86 are 8bit

I agree make a ng which would be true 64bit aka the itanium and ps3. The real amgia clones.

9:45 AM  
Blogger Hombre said...

It's too small a project for that and it too well suited to older non-64bit machines.

there is no true 64bit on x86 yeah the amiga os has it . All x86 are 8bit

I agree make a ng which would be true 64bit aka the itanium and ps3. The real amgia clones.

9:46 AM  

Post a Comment

<< Home