Update of /cvsroot/oprofile/oprofile
In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv30655
Modified Files:
HACKING README
Log Message:
Updates for Maynard.
Index: HACKING
===================================================================
RCS file: /cvsroot/oprofile/oprofile/HACKING,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -p -d -r1.13 -r1.14
--- HACKING 2 Aug 2005 17:33:19 -0000 1.13
+++ HACKING 4 Jul 2008 15:50:58 -0000 1.14
@@ -106,16 +106,17 @@ but a notification of what needs changin
affect the docs (man-pages or oprofile.xml) must include documentation updates
as appropriate. Also see below.
-You may after a while be given direct commit rights. You should be subscribed
-to both the main list and the commits mailing list if you do. Your cvs commit
-message only needs to briefly describe what your change does - the change log
-should have the detailed description. Any non-trivial change needs approval
-from either John or Phil, unless stated otherwise. The CVS tree will freeze
-occassionally for release, in which case no commits are allowed at all without
-agreement of John and Phil. CVS admin changes (-kb, .cvsignore etc.) do not
-need a change log, and neither does changes to TODO. If you make a change
-that affects the user (feature improvement, new feature, bug fix, UI change),
-see the next section.
+You may after a while be given direct commit rights. You should be
+subscribed to both the main list and the commits mailing list if you do.
+Your cvs commit message only needs to briefly describe what your change
+does - the change log should have the detailed description. Any
+non-trivial change needs approval from either John, Phil or Maynard,
+unless stated otherwise. The CVS tree will freeze occassionally for
+release, in which case no commits are allowed at all without agreement
+of John, Phil, or Maynard. CVS admin changes (-kb, .cvsignore etc.) do
+not need a change log, and neither does changes to TODO. If you make a
+change that affects the user (feature improvement, new feature, bug fix,
+UI change), see the next section.
The oprofile website
--------------------
Index: README
===================================================================
RCS file: /cvsroot/oprofile/oprofile/README,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -p -d -r1.27 -r1.28
--- README 12 Dec 2004 23:26:34 -0000 1.27
+++ README 4 Jul 2008 15:50:58 -0000 1.28
@@ -8,6 +8,8 @@ Please visit the oprofile website at : h
oprofile was written by John Levon <levon@...>
and Philippe Elie <phil.el@...>.
+Maynard Johnson <maynardj@...> is the current maintainer.
+
Dave Jones <davej@...> provided bug fixes and support for
the AMD Athlon, and AMD Hammer families of CPUs.

Update of /cvsroot/oprofile/oprofile
In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv10002
Modified Files:
ChangeLog README_PACKAGERS
Log Message:
Add more advice to packagers regarding the new JIT support libraries
Index: ChangeLog
===================================================================
RCS file: /cvsroot/oprofile/oprofile/ChangeLog,v
retrieving revision 1.1820
retrieving revision 1.1821
diff -u -p -d -r1.1820 -r1.1821
--- ChangeLog 3 Jul 2008 16:20:15 -0000 1.1820
+++ ChangeLog 3 Jul 2008 16:35:21 -0000 1.1821
@@ -1,4 +1,9 @@
-2008-07-01 Maynard Johnson <maynardj@...>
+2008-07-03 Maynard Johnson <maynardj@...>
+ * ChangeLog: Correct date of previous entry
+ * README_PACKAGERS: Add more advice to packagers
+ regarding the new JIT support libraries
+
+2008-07-03 Maynard Johnson <maynardj@...>
* libopagent/Makefile.am:
* libopagent/opagent.c:
Index: README_PACKAGERS
===================================================================
RCS file: /cvsroot/oprofile/oprofile/README_PACKAGERS,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -d -r1.2 -r1.3
--- README_PACKAGERS 28 Apr 2008 21:23:25 -0000 1.2
+++ README_PACKAGERS 3 Jul 2008 16:35:21 -0000 1.3
@@ -5,13 +5,60 @@ When building an RPM for OProfile, pleas
described in:
http://www.rpm.org/RPM-HOWTO/build.html
+
+New file to install as of release 0.9.3
+---------------------------------------
+
+As of release 0.9.3, opreport is capable of generating XML output.
+Tool developers who wish to use the xml output will need to have
+access to the doc/opreport.xsd file, which describes the schema.
+RPM packagers may install this file in the same package as the other
+standard OProfile components or in a separate devel package if desired.
+
+
+New files to install as of release 0.9.4
+---------------------------------------
+
+As of release 0.9.4, OProfile includes a JIT support library called libopagent.
+This library is needed at runtime when profiling JITed code from supported
+virtual machines. The install location for this library is:
+ <libdir>/oprofile
+
+OProfile also includes support for profiling Java applications. This support
+must be configured by way of the '--with-java=<path_to_jdk>' configure
+option. If your JDK is older than version 1.5, only a JVMPI agent library
+is built. If your JDK is version 1.5, both JVMPI and JVMTI agent
+libraries are built. If your JDK is 1.6 or newer, only the JVMTI agent
+library is built. As with libopagent described above, the install location
+for these is '<libdir>/oprofile'.
+
+RPM packagers can install the <libdir>/oprofile libraries in the same package
+as the other standard OProfile components or in a separate package if desired.
+It is recommended to run ldconfig in %post and %postun to add/remove the
+<libdir>/oprofile path from the standard library search paths.
+
+On bi-arch platforms that support more than one "bitness" of userspace software
+(e.g., 32-bit and 64-bit programs), it is recommended that the libopagent and
+Java agent libraries be packaged in a separate RPM. You could then build
+OProfile twice -- once for each bitness type. You would then distribute both
+versions of the RPMs containing the libraries, but only one RPM containing the
+"base" OProfile (i.e., executables, scripts, etc.).
+
+The new JIT support also provides the ability for third parties to develop
+JIT agents for other virtual machines. The development files provided for this
+purpose are:
+ doc/op-jit-devel.html
+ include/opagent.h
+
+Again, the RPM packager may package these files in the default package
+or in a separate devel package.
+
+
Requirement for building a binary RPM package
----------------------------------------
OProfile requires the special user account "oprofile" to exist for purposes
-of processing samples from JIT'ed code (e.g., Java applications). The build
-process is implemented to warn during 'configure' step and to fail and exit
-during 'make install' step if the special user account does not exist.
+of processing samples from JIT'ed code (e.g., Java applications).
When defining the spec file for the OProfile RPM, you should add the automatic
creation of the special "oprofile" user account. Please refer to the URL