forked from Cuju-ft/Cuju
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5,195 changed files
with
1,745,778 additions
and
2 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,129 @@ | ||
| /config-devices.* | ||
| /config-all-devices.* | ||
| /config-all-disas.* | ||
| /config-host.* | ||
| /config-target.* | ||
| /config.status | ||
| /config-temp | ||
| /trace-events-all | ||
| /trace/generated-tracers.h | ||
| /trace/generated-tracers.c | ||
| /trace/generated-tracers-dtrace.h | ||
| /trace/generated-tracers.dtrace | ||
| /trace/generated-events.h | ||
| /trace/generated-events.c | ||
| /trace/generated-helpers-wrappers.h | ||
| /trace/generated-helpers.h | ||
| /trace/generated-helpers.c | ||
| /trace/generated-tcg-tracers.h | ||
| /trace/generated-ust-provider.h | ||
| /trace/generated-ust.c | ||
| /ui/shader/texture-blit-frag.h | ||
| /ui/shader/texture-blit-vert.h | ||
| *-timestamp | ||
| /*-softmmu | ||
| /*-darwin-user | ||
| /*-linux-user | ||
| /*-bsd-user | ||
| /ivshmem-client | ||
| /ivshmem-server | ||
| /libdis* | ||
| /libuser | ||
| /linux-headers/asm | ||
| /qga/qapi-generated | ||
| /qapi-generated | ||
| /qapi-types.[ch] | ||
| /qapi-visit.[ch] | ||
| /qapi-event.[ch] | ||
| /qmp-commands.h | ||
| /qmp-introspect.[ch] | ||
| /qmp-marshal.c | ||
| /qemu-doc.html | ||
| /qemu-doc.info | ||
| /qemu-img | ||
| /qemu-nbd | ||
| /qemu-options.def | ||
| /qemu-options.texi | ||
| /qemu-img-cmds.texi | ||
| /qemu-img-cmds.h | ||
| /qemu-io | ||
| /qemu-ga | ||
| /qemu-bridge-helper | ||
| /qemu-monitor.texi | ||
| /qemu-monitor-info.texi | ||
| /qemu-version.h | ||
| /qemu-version.h.tmp | ||
| /module_block.h | ||
| /vscclient | ||
| /fsdev/virtfs-proxy-helper | ||
| *.[1-9] | ||
| *.a | ||
| *.aux | ||
| *.cp | ||
| *.dvi | ||
| *.exe | ||
| *.msi | ||
| *.dll | ||
| *.so | ||
| *.mo | ||
| *.fn | ||
| *.ky | ||
| *.log | ||
| *.pod | ||
| *.cps | ||
| *.fns | ||
| *.kys | ||
| *.pg | ||
| *.pyc | ||
| *.toc | ||
| *.tp | ||
| *.vr | ||
| *.d | ||
| !/scripts/qemu-guest-agent/fsfreeze-hook.d | ||
| *.o | ||
| *.lo | ||
| *.la | ||
| *.pc | ||
| .libs | ||
| .sdk | ||
| *.gcda | ||
| *.gcno | ||
| /pc-bios/bios-pq/status | ||
| /pc-bios/vgabios-pq/status | ||
| /pc-bios/optionrom/linuxboot.asm | ||
| /pc-bios/optionrom/linuxboot.bin | ||
| /pc-bios/optionrom/linuxboot.raw | ||
| /pc-bios/optionrom/linuxboot.img | ||
| /pc-bios/optionrom/linuxboot_dma.asm | ||
| /pc-bios/optionrom/linuxboot_dma.bin | ||
| /pc-bios/optionrom/linuxboot_dma.raw | ||
| /pc-bios/optionrom/linuxboot_dma.img | ||
| /pc-bios/optionrom/multiboot.asm | ||
| /pc-bios/optionrom/multiboot.bin | ||
| /pc-bios/optionrom/multiboot.raw | ||
| /pc-bios/optionrom/multiboot.img | ||
| /pc-bios/optionrom/kvmvapic.asm | ||
| /pc-bios/optionrom/kvmvapic.bin | ||
| /pc-bios/optionrom/kvmvapic.raw | ||
| /pc-bios/optionrom/kvmvapic.img | ||
| /pc-bios/s390-ccw/s390-ccw.elf | ||
| /pc-bios/s390-ccw/s390-ccw.img | ||
| .stgit-* | ||
| cscope.* | ||
| tags | ||
| TAGS | ||
| docker-src.* | ||
| *~ | ||
| *.flat | ||
| .*.cmd | ||
| *.ko | ||
| *.mod.c | ||
| config.mak | ||
| kvm-kmod-config.h | ||
| modules.order | ||
| Module.symvers | ||
| Modules.symvers | ||
| Module.markers | ||
| .tmp_versions | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,118 @@ | ||
| QEMU Coding Style | ||
| ================= | ||
|
|
||
| Please use the script checkpatch.pl in the scripts directory to check | ||
| patches before submitting. | ||
|
|
||
| 1. Whitespace | ||
|
|
||
| Of course, the most important aspect in any coding style is whitespace. | ||
| Crusty old coders who have trouble spotting the glasses on their noses | ||
| can tell the difference between a tab and eight spaces from a distance | ||
| of approximately fifteen parsecs. Many a flamewar has been fought and | ||
| lost on this issue. | ||
|
|
||
| QEMU indents are four spaces. Tabs are never used, except in Makefiles | ||
| where they have been irreversibly coded into the syntax. | ||
| Spaces of course are superior to tabs because: | ||
|
|
||
| - You have just one way to specify whitespace, not two. Ambiguity breeds | ||
| mistakes. | ||
| - The confusion surrounding 'use tabs to indent, spaces to justify' is gone. | ||
| - Tab indents push your code to the right, making your screen seriously | ||
| unbalanced. | ||
| - Tabs will be rendered incorrectly on editors who are misconfigured not | ||
| to use tab stops of eight positions. | ||
| - Tabs are rendered badly in patches, causing off-by-one errors in almost | ||
| every line. | ||
| - It is the QEMU coding style. | ||
|
|
||
| Do not leave whitespace dangling off the ends of lines. | ||
|
|
||
| 2. Line width | ||
|
|
||
| Lines should be 80 characters; try not to make them longer. | ||
|
|
||
| Sometimes it is hard to do, especially when dealing with QEMU subsystems | ||
| that use long function or symbol names. Even in that case, do not make | ||
| lines much longer than 80 characters. | ||
|
|
||
| Rationale: | ||
| - Some people like to tile their 24" screens with a 6x4 matrix of 80x24 | ||
| xterms and use vi in all of them. The best way to punish them is to | ||
| let them keep doing it. | ||
| - Code and especially patches is much more readable if limited to a sane | ||
| line length. Eighty is traditional. | ||
| - The four-space indentation makes the most common excuse ("But look | ||
| at all that white space on the left!") moot. | ||
| - It is the QEMU coding style. | ||
|
|
||
| 3. Naming | ||
|
|
||
| Variables are lower_case_with_underscores; easy to type and read. Structured | ||
| type names are in CamelCase; harder to type but standing out. Enum type | ||
| names and function type names should also be in CamelCase. Scalar type | ||
| names are lower_case_with_underscores_ending_with_a_t, like the POSIX | ||
| uint64_t and family. Note that this last convention contradicts POSIX | ||
| and is therefore likely to be changed. | ||
|
|
||
| When wrapping standard library functions, use the prefix qemu_ to alert | ||
| readers that they are seeing a wrapped version; otherwise avoid this prefix. | ||
|
|
||
| 4. Block structure | ||
|
|
||
| Every indented statement is braced; even if the block contains just one | ||
| statement. The opening brace is on the line that contains the control | ||
| flow statement that introduces the new block; the closing brace is on the | ||
| same line as the else keyword, or on a line by itself if there is no else | ||
| keyword. Example: | ||
|
|
||
| if (a == 5) { | ||
| printf("a was 5.\n"); | ||
| } else if (a == 6) { | ||
| printf("a was 6.\n"); | ||
| } else { | ||
| printf("a was something else entirely.\n"); | ||
| } | ||
|
|
||
| Note that 'else if' is considered a single statement; otherwise a long if/ | ||
| else if/else if/.../else sequence would need an indent for every else | ||
| statement. | ||
|
|
||
| An exception is the opening brace for a function; for reasons of tradition | ||
| and clarity it comes on a line by itself: | ||
|
|
||
| void a_function(void) | ||
| { | ||
| do_something(); | ||
| } | ||
|
|
||
| Rationale: a consistent (except for functions...) bracing style reduces | ||
| ambiguity and avoids needless churn when lines are added or removed. | ||
| Furthermore, it is the QEMU coding style. | ||
|
|
||
| 5. Declarations | ||
|
|
||
| Mixed declarations (interleaving statements and declarations within | ||
| blocks) are generally not allowed; declarations should be at the beginning | ||
| of blocks. | ||
|
|
||
| Every now and then, an exception is made for declarations inside a | ||
| #ifdef or #ifndef block: if the code looks nicer, such declarations can | ||
| be placed at the top of the block even if there are statements above. | ||
| On the other hand, however, it's often best to move that #ifdef/#ifndef | ||
| block to a separate function altogether. | ||
|
|
||
| 6. Conditional statements | ||
|
|
||
| When comparing a variable for (in)equality with a constant, list the | ||
| constant on the right, as in: | ||
|
|
||
| if (a == 1) { | ||
| /* Reads like: "If a equals 1" */ | ||
| do_something(); | ||
| } | ||
|
|
||
| Rationale: Yoda conditions (as in 'if (1 == a)') are awkward to read. | ||
| Besides, good compilers already warn users when '==' is mis-typed as '=', | ||
| even when the constant is on the right. |
Oops, something went wrong.