QemuMachineDevelopment - Revision history

VeroniqueL at 15:23, 1 September 2009

2009-09-01T15:23:29Z

JulienPeeters: /* Introduction */

2008-09-27T20:28:28Z

‎Introduction

JulienPeeters: /* Introduction */

2008-09-27T20:27:45Z

‎Introduction

JulienPeeters: /* Introduction */

2008-09-27T20:27:30Z

‎Introduction

JulienPeeters: /* Source trees */

2008-09-27T20:25:48Z

‎Source trees

JulienPeeters at 15:52, 22 June 2008

2008-06-22T15:52:54Z

JulienPeeters: /* Improve Qemu understanding */

2008-06-22T15:51:59Z

‎Improve Qemu understanding

JulienPeeters at 13:30, 22 June 2008

2008-06-22T13:30:24Z

JulienPeeters at 13:29, 22 June 2008

2008-06-22T13:29:32Z

JulienPeeters at 13:24, 22 June 2008

2008-06-22T13:24:55Z

@@ Line 1: / Line 1: @@
 == Introduction ==
-The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.
+The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software as if it were running on a real board.
 In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).
@@ Line 57: / Line 57: @@
 All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations independently of targets.
-The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every functions you should need to talk with the emulated environment are defined there. In consequences, the first point of our work is to understand the behavior of Qemu through these lines.
+The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every function you should need to talk with the emulated environment is defined there. Consequently, the first point of our work is to understand the behavior of Qemu through these lines.
 === The Target specific code ===

@@ Line 4: / Line 4: @@
 In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).
-'''See FireBoard project in the Contest 2008 page [[Contest]].'''
+'''See FireBoard project in the [[Contest | Contest 2008]] page.'''
 == Armadeus boards devices ==

@@ Line 4: / Line 4: @@
 In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).
-See FireBoard project in the Contest 2008 page [[Contest]].
+'''See FireBoard project in the Contest 2008 page [[Contest]].'''
 == Armadeus boards devices ==

@@ Line 1: / Line 1: @@
 == Introduction ==
 The aim of this project is to provide a fully functional and user-friendly way for developers and people interested in the Armadeus Project to test software like if it is running on a real board.
 In a far-off time, the aim is to provide a small framework to build dynamic software tests and run them automatically (after a static analysis of code for instance in order to build a fully featured report).
 == Armadeus boards devices ==

← Older revision		Revision as of 20:25, 27 September 2008
Line 45:		Line 45:
	\|}		\|}

−	~~== Source trees ==~~

−	~~Firstly, you have to install Subversion and Git packages~~
−
−	~~On Debian/Ubuntu (any version) :~~
−	~~<pre>~~
−	~~[myhome] # apt-get install subversion git-core~~
−	~~</pre>~~
−
−	~~On Gentoo~~
−	~~<pre>~~
−	~~[myhome] # emerge dev-util/subversion dev-util/git~~
−	~~</pre>~~
−
−	~~You can download the official QEMU svn tree here :~~
−
−	~~<pre>~~
−	~~[my-repos] $ svn co svn://svn.savannah.nongnu.org/qemu/trunk~~
−	~~</pre>~~
−
−	~~And [[User:JulienPeeters \| my ]] git repository where to find Armadeus DevFull board hardware emulation (Coming soon and depends on the interest people have in this project) :~~
−
−	~~<pre>~~
−	~~[my-repos] $ git clone git://dedilabs.com/~jpeeters/qemu-jpeeters~~
−	~~</pre>~~

	== Qemu mechanisms : Qemu separated in three parts ==		== Qemu mechanisms : Qemu separated in three parts ==

@@ Line 79: / Line 79: @@
 Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.
-All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations for the different targets.
+All the code of the TCG (Tiny Code Generator) is placed in the tcg directory of the source tree and contains implementations independently of targets.
 The entry point of Qemu is placed in the vl.c file. After reading it, you could see that the major part of Qemu is contained in it. Every functions you should need to talk with the emulated environment are defined there. In consequences, the first point of our work is to understand the behavior of Qemu through these lines.
@@ Line 85: / Line 85: @@
 === The Target specific code ===
-It's not alredy clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").
+It's not already clear to me where are placed the Qemu target specific code. So, at this time, it looks like there is mainly situated in the target-X directory (X have to be replaced by the target name, like "arm").
 === The hardware emulation layer ===

@@ Line 75: / Line 75: @@
 Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.
-=== The code translation and the emulation core system ===
+=== The code translation and the emulation system core ===
 Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.

@@ Line 71: / Line 71: @@
 </pre>
-== Understanding of the Qemu functions ==
+== Qemu mechanisms : Qemu separated in three parts ==
 Qemu is a wide software in which it could be difficult to land up. So a little explanation have to be done.
-=== Qemu separated in two parts ===
+=== The code translation and the emulation core system ===
-−
-==== The code translation and the emulation core system ====
 Qemu integrates a dynamic code translation "machine" which translates target instructions in host ones on the fly. They all are already implemented in Qemu, so we have not them to remake. But this part of code is heavy compact and need knowledge in both host and target instructions set in order to understand it.
@@ Line 84: / Line 82: @@
 Qemu is also composed of a common emulation system mainly contained in the vl.c file (in the root of the source tree). Every function which manage the emulation system are placed in this file.
 ==Links==