1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
This text describes contribution procedures to systemtap. Please read
and understand them before jumping in. Discussions take place on
the <systemtap@sources.redhat.com> mailing list.
- general
Submissions should be in an easy-to-read diff/patch form, unless
this is inappropriate due to size, relevance, or fraction of novel
content. They should be accompanied by an explanation, and
ChangeLog entries. The relevant test suites should be run before
and after your changes, and regressions avoided, explained, or
corrected.
Established contributors may be considered for direct CVS write
access. Other contributors should simply pack up the goods into a
plain text email message to the mailing list.
- obvious changes
Trivial, obvious patches may be posted or committed without other
formalities.
- copyright
You must designate the appropriate copyright holder for your
contribution. If not already there, this name should be added by
your patch to the copyright header in the affected files. The
copyright holder is assumed to agree with the general licensing
terms (GPLv2+).
- coding style
Abide by the general formatting of the code you are modifying. The
code base generally follows the GNU standards. ChangeLog entries
are used for nontrivial changes to source or documentation files.
Some subdirectories have ChangeLog files of their own, so make sure
you find the correct ones to prepend.
- test suites
As far as practicable, changes should be accompanied by test cases
to prevent future regressions. Tests should be run on at least
x86, and ideally also on some 64-bit platform. The test suite is
located under /src/testsuite and is based on dejagnu. "make check"
runs unprivileged tests only against an uninstalled build tree.
"make installcheck" runs all tests against an installed tree.
Tests that don't require probe execution should go into new or
modified files under the *{ok,ko} directories, which are scanned
by corresponding systemtap.pass1-4/*.exp files. The "ko" tests are
for expected (deliberate) errors.
Tests that execute probes (pass 5) should include their own .exp/.stp
files under any other appropriate systemtap.* testsuite subdirectory.
- translator
Translator changes can easily invalidate tapsets and user script
code. One must tread carefully and run regression tests rigorously.
Both positive and negative polarity (expect-pass / expect-fail) test
cases may need to be written to assert a bug fix. Script language
changes should be documented in the stap.1 man page.
- tapsets
Tapset script files should demonstrate effective economy, and avoid
conflicts with user and other tapset code.
It may be necessary to prefix symbols with the tapset name to ensure
systemtap-wide uniqueness. All "external interfaces" expected to be
used by user scripts (or perhaps other tapsets) should be documented
in stapfuncs.5, stapprobes.5. Internal function, variable, probe
identifiers should be prefixed with "_" for extra uniqueness, and
not documented in the man pages.
Tapsets should come with a tests cases that provide good test coverage.
Every alias definition should be tested for pass-2 correctness. Every
embedded-C routine should be tested for pass-4 buildability and ideally
pass-5 correctness. The platforms/architectures against which the tapset
was tested should be published, and ideally asserted by code.
Embedded-C code should avoid making references to the runtime or
other code possibly generated by the translator.
- runtime
Changes to the runtime can cause problems on different architectures
or kernel versions. Luckily, many code mistakes show up easily in
the pass-4 tests. [hunt: if appropriate, fill in information for
runtime self-testing code]
- meta
Proposed changes to these guidelines should be discussed on the
mailing list.
|