Device Driver Reuse

View: New views
4 Messages — Rating Filter:   Alert me  

Device Driver Reuse

by Roberto Jung Drebes-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hello there,

Is there anyone still working on the afterburner project? I'm trying  
to make some experiments with the device driver reuse framework, but  
have some questions about it. I contacted Josh LeVasseur but he told  
me he's not working on it anymore, unfortunately.

I already downloaded the afterburner sourcecode through mercurial but  
am lost about how to setup the supporting environment. Tried to build  
the documentation but the figures are missing.

Any tips?

Thanks in advance,

--
Roberto Jung Drebes - Tokyo, Japan
<drebes@...>
http://japao.drebes.org/









RE: Device Driver Reuse

by Jan Stoess-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Roberto,

Yes there are still people (me) working on the afterburner. Mostly internal prototyping though, far less attention is spent to the external project pages.

Here's a quick suggestion on getting UP afterburner/pre-virtualization to work (I've sent that to l4ka a while ago):

- Download the afterburner via mercurial
- No need to download pistachio or IDL tools etc., the afterburner make script will download it
- check out and inspect the sample config.out files in afterburner/configs, e.g.,
  - choose sample-config.out if you'd like to have para-virtualized linux guests
  - choose sample-config-hvm.out if you'd like fully-virtualized guests (WARNING: WORK IN PROGRESS). Works only with Intel VMX
- create a build directory, run "make -f path/to/afterburner/Makefile", copy your favorite sample config into "build/config.out", run "make menuconfig" to edit the settings, finally run "make world", which will produce binaries in "build/boot"
- make "run-qemu" runs the afterburner in qemu

Just a quick tip: use gcc and g++ Versions 3, e.g. by running make CC=gcc3 CXX=g++3, or by putting "CC=gcc3" and "CXX=g++3" into the local build Makefile.

-Jan


--
Jan Stoess
System Architecture Group
University of Karlsruhe
Phone: +49 (721) 608-4056
Fax: +49 (721) 608-7664
eMail: stoess@...

--
Jan Stoess
KIT/UKa System Architecture Group
Phone: +49 (721) 608-4056
Fax: +49 (721) 608-7664
eMail: stoess@...


> -----Original Message-----
> From: l4ka-bounces@... [mailto:l4ka-bounces@...-
> karlsruhe.de] On Behalf Of Roberto Jung Drebes
> Sent: Friday, October 23, 2009 7:18 AM
> To: l4ka@...
> Subject: Device Driver Reuse
>
>
> Hello there,
>
> Is there anyone still working on the afterburner project? I'm trying
> to make some experiments with the device driver reuse framework, but
> have some questions about it. I contacted Josh LeVasseur but he told
> me he's not working on it anymore, unfortunately.
>
> I already downloaded the afterburner sourcecode through mercurial but
> am lost about how to setup the supporting environment. Tried to build
> the documentation but the figures are missing.
>
> Any tips?
>
> Thanks in advance,
>
> --
> Roberto Jung Drebes - Tokyo, Japan
> <drebes@...>
> http://japao.drebes.org/
>
>
>
>
>
>
>



Re: Device Driver Reuse

by Roberto Jung Drebes-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hello Jan,

Thanks for your reply.

I've tried building it, but I get a

cc1: error: -mpreferred-stack-boundary=2 is not between 4 and 12

error when trying to build dietlibc. Is this error from trying to  
compile it with gcc 4?

My system doesn't have gcc 3 by default, so the first make command  
says that gcc 3 will be build. But when inspecting the generated  
config.out with menuconfig, the build gcc option is still disabled.  
Even after manually enabling it, I still get the same error.

Actually, I could manage to install gcc-3.4.6 from my distribution,  
but g++ is unavailable (Ubuntu 9.4).

Is there any other tip to getting it to build?

Regards,

Roberto.


On 23/10/2009, at 20:26, Jan Stoess wrote:

> Hi Roberto,
>
> Yes there are still people (me) working on the afterburner. Mostly  
> internal prototyping though, far less attention is spent to the  
> external project pages.
>
> Here's a quick suggestion on getting UP afterburner/pre-
> virtualization to work (I've sent that to l4ka a while ago):
>
> - Download the afterburner via mercurial
> - No need to download pistachio or IDL tools etc., the afterburner  
> make script will download it
> - check out and inspect the sample config.out files in afterburner/
> configs, e.g.,
>  - choose sample-config.out if you'd like to have para-virtualized  
> linux guests
>  - choose sample-config-hvm.out if you'd like fully-virtualized  
> guests (WARNING: WORK IN PROGRESS). Works only with Intel VMX
> - create a build directory, run "make -f path/to/afterburner/
> Makefile", copy your favorite sample config into "build/config.out",  
> run "make menuconfig" to edit the settings, finally run "make  
> world", which will produce binaries in "build/boot"
> - make "run-qemu" runs the afterburner in qemu
>
> Just a quick tip: use gcc and g++ Versions 3, e.g. by running make  
> CC=gcc3 CXX=g++3, or by putting "CC=gcc3" and "CXX=g++3" into the  
> local build Makefile.
>
> -Jan


--
Roberto Jung Drebes - Tokyo, Japan
<drebes@...>
http://japao.drebes.org/









RE: Device Driver Reuse

by Jan Stoess-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Roberto,

I've added a small fix to the repo that lets the build infrastructure use gcc for all the external support stuff (e.g., dietlibc) as well. Can you please update your HG repo and tell me whether compiling dietlibc works now?

Thanks,
-Jan

--
Jan Stoess
KIT/UKa System Architecture Group
Phone: +49 (721) 608-4056
Fax: +49 (721) 608-7664
eMail: stoess@...