Skip to content

Commit 68396ea

Browse files
rmustaccrmustacc
committed
Initial commit of d32e8d0b8d9e0ef7cf7ab2e74548982972789dfc from qemu-kvm
0 parents  commit 68396ea

File tree

1,627 files changed

+711652
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,627 files changed

+711652
-0
lines changed

‎.gitignore

+64
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
config-devices.*
2+
config-all-devices.*
3+
config-host.*
4+
config-target.*
5+
trace.h
6+
trace.c
7+
trace-dtrace.h
8+
trace-dtrace.dtrace
9+
*-timestamp
10+
*-softmmu
11+
*-darwin-user
12+
*-linux-user
13+
*-bsd-user
14+
libdis*
15+
libhw32
16+
libhw64
17+
libuser
18+
qemu-doc.html
19+
qemu-tech.html
20+
qemu-doc.info
21+
qemu-tech.info
22+
qemu.1
23+
qemu.pod
24+
qemu-img.1
25+
qemu-img.pod
26+
qemu-img
27+
qemu-nbd
28+
qemu-nbd.8
29+
qemu-nbd.pod
30+
qemu-options.def
31+
qemu-options.texi
32+
qemu-img-cmds.texi
33+
qemu-img-cmds.h
34+
qemu-io
35+
qemu-monitor.texi
36+
QMP/qmp-commands.txt
37+
.gdbinit
38+
*.a
39+
*.aux
40+
*.cp
41+
*.dvi
42+
*.exe
43+
*.fn
44+
*.ky
45+
*.log
46+
*.pdf
47+
*.pg
48+
*.pyc
49+
*.toc
50+
*.tp
51+
*.vr
52+
*.d
53+
*.o
54+
.pc
55+
patches
56+
pc-bios/bios-pq/status
57+
pc-bios/vgabios-pq/status
58+
pc-bios/optionrom/linuxboot.bin
59+
pc-bios/optionrom/multiboot.bin
60+
pc-bios/optionrom/multiboot.raw
61+
pc-bios/optionrom/extboot.bin
62+
pc-bios/optionrom/vapic.bin
63+
.stgit-*
64+
cscope.*

‎.gitmodules

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
[submodule "roms/vgabios"]
2+
path = roms/vgabios
3+
url = git://git.kernel.org/pub/scm/virt/kvm/vgabios.git/
4+
[submodule "roms/seabios"]
5+
path = roms/seabios
6+
url = git://git.qemu.org/seabios.git/

‎CODING_STYLE

+81
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
Qemu Coding Style
2+
=================
3+
4+
Please use the script checkpatch.pl in the scripts directory to check
5+
patches before submitting.
6+
7+
1. Whitespace
8+
9+
Of course, the most important aspect in any coding style is whitespace.
10+
Crusty old coders who have trouble spotting the glasses on their noses
11+
can tell the difference between a tab and eight spaces from a distance
12+
of approximately fifteen parsecs. Many a flamewar have been fought and
13+
lost on this issue.
14+
15+
QEMU indents are four spaces. Tabs are never used, except in Makefiles
16+
where they have been irreversibly coded into the syntax.
17+
Spaces of course are superior to tabs because:
18+
19+
- You have just one way to specify whitespace, not two. Ambiguity breeds
20+
mistakes.
21+
- The confusion surrounding 'use tabs to indent, spaces to justify' is gone.
22+
- Tab indents push your code to the right, making your screen seriously
23+
unbalanced.
24+
- Tabs will be rendered incorrectly on editors who are misconfigured not
25+
to use tab stops of eight positions.
26+
- Tabs are rendered badly in patches, causing off-by-one errors in almost
27+
every line.
28+
- It is the QEMU coding style.
29+
30+
Do not leave whitespace dangling off the ends of lines.
31+
32+
2. Line width
33+
34+
Lines are 80 characters; not longer.
35+
36+
Rationale:
37+
- Some people like to tile their 24" screens with a 6x4 matrix of 80x24
38+
xterms and use vi in all of them. The best way to punish them is to
39+
let them keep doing it.
40+
- Code and especially patches is much more readable if limited to a sane
41+
line length. Eighty is traditional.
42+
- It is the QEMU coding style.
43+
44+
3. Naming
45+
46+
Variables are lower_case_with_underscores; easy to type and read. Structured
47+
type names are in CamelCase; harder to type but standing out. Scalar type
48+
names are lower_case_with_underscores_ending_with_a_t, like the POSIX
49+
uint64_t and family. Note that this last convention contradicts POSIX
50+
and is therefore likely to be changed.
51+
52+
When wrapping standard library functions, use the prefix qemu_ to alert
53+
readers that they are seeing a wrapped version; otherwise avoid this prefix.
54+
55+
4. Block structure
56+
57+
Every indented statement is braced; even if the block contains just one
58+
statement. The opening brace is on the line that contains the control
59+
flow statement that introduces the new block; the closing brace is on the
60+
same line as the else keyword, or on a line by itself if there is no else
61+
keyword. Example:
62+
63+
if (a == 5) {
64+
printf("a was 5.\n");
65+
} else if (a == 6) {
66+
printf("a was 6.\n");
67+
} else {
68+
printf("a was something else entirely.\n");
69+
}
70+
71+
An exception is the opening brace for a function; for reasons of tradition
72+
and clarity it comes on a line by itself:
73+
74+
void a_function(void)
75+
{
76+
do_something();
77+
}
78+
79+
Rationale: a consistent (except for functions...) bracing style reduces
80+
ambiguity and avoids needless churn when lines are added or removed.
81+
Furthermore, it is the QEMU coding style.

0 commit comments

Comments
 (0)