summaryrefslogtreecommitdiffstats
path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* Test wprintf() in addition to printf().das2009-01-311-3/+19
|
* Add tests for conj{,f,l}() that I wrote some time ago. These test thedas2009-01-313-1/+169
| | | | versions in libm, not the gcc builtins.
* track hal changessam2009-01-291-1/+3
|
* update for hal changessam2009-01-292-456/+239
|
* - Update my copyright.jeff2009-01-221-16/+27
| | | | | | | | - Print human readable time as a float with two digits of precision. Use ns now as well since clock periods are well into the hundreds of picoseconds now. - Show the average duration in the stats frame. This is often more useful than total duration.
* - Permit timestamps to be as far as 2048 ticks apart before we complainjeff2009-01-201-20/+54
| | | | | | | | | | | | | | | | about invalid timestamps. Nehalem CPUs seem to be synchronized but only within a fraction of a microsecond. - Make the Counter code more flexible to poor timestamps. In general we now complain a lot but render as much as we can. - Change the scaler behavior so it works better with very long and very short traces. We now set the maximum scale such that it properly displays the entire file by default and doesn't permit zooming out beyond the file. This improves other awkward navigation behavior. The interval is now set very small which can't be achieved by simply dragging the mouse. Clicking to the left of or right of the scaler bar will produce increments of a single, very small, interval now. Sponsored by: Nokia
* - Add summary information to the title once the file is parsed rather thanjeff2009-01-181-24/+36
| | | | | | | | | | printing it to the terminal. Now only parse errors go to the terminal. - Speedup drawing by raising and lowering tags only once everything has been drawn. Surprisingly, it now takes a little longer to parse than it does to draw. - Parameterize the layout with X_ and Y_ defines that determine the sizes of various things. - Remove unnecessary tags.
* - Significantly speedup hiding and displaying multiple rows by writing anjeff2009-01-181-31/+224
| | | | | | | | | | | | optimized single pass function for each. This reduces the number of tkinter calls required to the minimum. - Add a right-click context menu for sources. Supported commands hide the source, hide the whole group the source is in, and bring up a stat window. - Add a source stat frame that gives an event frequency table as well as the total duration for each event type that has a duration. This can be used to see, for example, the total time a thread spent running or blocked by a wchan or lock.
* Fix typophk2009-01-171-1/+1
| | | | Spotted by: juli
* Release the evil twin of nanobsd.sh: sysbuild.shphk2009-01-172-0/+681
| | | | | | | | | | | | | | | | | | | | quoth the README: I have been running -current on my laptop since before FreeBSD 2.0 was released and along the way developed this little trick to making the task easier. sysbuild.sh is a way to build a new FreeBSD system on a computer from a specification, while leaving the current installation intact. sysbuild.sh assume you have two partitions that can hold your rootfs and can be booted, and roughly speaking, all it does is build a new system into the one you don't use, from the one you do use. A partition named /freebsd is assumed to be part of your layout, and that is where the sources and ports will be found. If you know how nanobsd works, you will find a lot of similarity.
* - Add a new source configuration menu option that allows hiding andjeff2009-01-171-4/+173
| | | | | | | displaying sources. - Add functions to the main SchedGraph to facilitate source hiding. The source is simply moved off screen and all other sources are moved to compensate.
* - Rewrite the parser to support the new generic schedgraph interface.jeff2009-01-171-1002/+608
| | | | | | | | | | | | | | | | | | | This no longer requires any custom classes or parsers to support new event types. - Add an optional command line argument for specifying the clock frequency in ghz. This is useful for traces that do not include KTR_SCHED. Sponsored by: Nokia - Add support for sorting rows by clicking and dragging them to their new position. - Add support for configuring the cpu background colors. - Improve the scaling so a better center is maintained as you zoom. This is not perfect due to precision loss with floats used in the window views. - Add new colors and a random assignment for unknown event types. A table is used for known event types. This is the only event specific information.
* Be more Solaris-friendly.pjd2009-01-162-4/+8
| | | | Submitted by: Milan Cermak <Milan.Cermak@Sun.COM>
* Allow jot(1) regression tests to be checked out on Windows filesystems.ed2009-01-162-1/+1
| | | | | | | | The jot(1) regression tests directory contained two tests named `wx' and `wX', which doesn't work on case insensitive filesystems. Rename `wX' to `wX1'. MFC after: 1 month
* add athrd tool that dumps ath hal regulatory info; note this is soon tosam2009-01-156-4/+2106
| | | | obsolete but commit now so it's available for anyone that's interested
* simple scripts to demonstrate tdma setupsam2009-01-142-0/+39
|
* Add support for two new event source types:jhb2009-01-131-2/+224
| | | | | | | | | | | | | | | | | | | - Callwheels traced via KTR_CALLOUT. Each CPU is assigned a callwheel source. The events on this source are the execution of individual callout routines. Each routine shows up as a green rectangle while it is executed and the event details include the function pointer and argument. - Locks traced via KTR_LOCK. Currently, each lock name is assigned an event source (since the existing KTR_LOCK traces only include lock names and not pointers). This does mean that if multiple locks of the same name are manipulated, the source line for that name may be confusing. However, for many cases this can be useful. Locks are blue when they are held and purple when contested. The contention support is a bit weak due to limitations in the rw_rlock() and mtx_lock_spin() logging messages currently. I also have not added support for contention on lockmgr, sx, or rmlocks yet. What is there now can be profitably used to examine activity on Giant however. - Expand the width of the event source names column a bit to allow for some of the longer names of these new source types.
* - Add some rudimentary support for sorting the list of event sourcesjhb2009-01-131-13/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | (threads, CPU load counters, etc.). Each source is tagged with a group and an order similar to the SYSINIT SI_SUB_* and SI_ORDER_*. After the file is parsed, all the sources are then sorted. Currently, the only affects of this are that the CPU loads are now sorted by CPU ID (so CPU 0 is always first). However, this makes it easier to add new types of event sources in the future and have them all clustered together instead of intertwined with threads. - Python lists perform insertions at the tail much faster than insertions at the head. For a trace that had a lot of events for a single event source, the constant insertions of new events to the head of the per-source event list caused a noticable slow down. To compensate, append new events to the end of the list during parsing and then reverse the list prior to drawing. - Somewhere in the tkinter internals the coordinates of a canvas are stored in a signed 32-bit integer. As a result, if an the box for an event spans 2^31, it would actually end up having a negative X offset at one end. The result was a single box that covered the entire event source. Kris worked around this for some traces by bumping up the initial ticks/pixel ratio from 1 to 10. However, a divisor of 10 can still be too small for large tracefiles (e.g. with 4 million entries). Instead of hardcoding the initial scaling ratio, calculate it from the time span of the trace file. - Add support for using the mouse wheel to scroll the graph window up and down.
* add tool to calculate air time for 802.11 packetssam2009-01-123-1/+604
|
* Vi got me in trouble in r187102 - fix typo of duplicate output filename.obrien2009-01-121-1/+1
| | | | Submitted by: several
* Update fech URL.obrien2009-01-121-1/+1
| | | | Submitted by: Alexander Best <alexbestms@math.uni-muenster.de>
* example configurations for cross-building to Gateworks 2348 and 2358 boards;sam2009-01-099-0/+773
| | | | | | probably needs cleanups to be less specific to my needs/uses MFC after: 2 weeks
* TDMA support for long distance point-to-point links using ath devices:sam2009-01-084-4/+21
| | | | | | | | | | | | | | | o add net80211 support for a tdma vap that is built on top of the existing adhoc-demo support o add tdma scheduling of frame transmission to the ath driver; it's conceivable other devices might be capable of this too in which case they can make use of the 802.11 protocol additions etc. o add minor bits to user tools that need to know: ifconfig to setup and configure, new statistics in athstats, and new debug mask bits While the architecture can support >2 slots in a TDMA BSS the current design is intended (and tested) for only 2 slots. Sponsored by: Intel
* Add a new program, ether_reflect, which is useful in testing ethernetgnn2008-12-234-0/+283
| | | | devices and switches.
* Fix a bug in the man page where we were not showing the correct flagsgnn2008-12-231-2/+2
| | | | | in the explanation. Several of the flags were -i, since it was a copy/paste operation.
* Add the mctest program and description to the README.gnn2008-12-231-0/+1
|
* Add new tool tionxcl to bring ttys out of exclusive mode whenbms2008-12-182-0/+107
| | | | left by e.g. legacy uucp or tip.
* Make it possible to cherry-pick packages out of a directory.phk2008-12-161-1/+6
|
* bring in diagnostic tools that are useful now that we have hal source codesam2008-12-0723-7/+4222
|
* This is simple testing program for revision 185647.ganbold2008-12-061-0/+81
| | | | | | | It invokes multiple parallel threads and each thread calls vfork() system call. Approved by: kib
* Update for 185401, errors now go to stderr.stefanf2008-11-281-0/+0
|
* Add tools-level test for POSIX.1e functionality.trasz2008-11-253-0/+632
| | | | Approved by: rwatson (mentor)
* This actually works on Linux, I just had wrong directory permission.pjd2008-11-241-4/+0
| | | | Found by: trasz
* Include TODO messages even if tests succeeds, so we can detect when somethingpjd2008-11-241-6/+18
| | | | suddenly started to work.
* Add a test for r185231.stefanf2008-11-231-0/+9
|
* Mark all the places where Linux is not POSIX-compilant. Tested on ext3.pjd2008-11-233-0/+8
|
* fstest for Linux:pjd2008-11-239-56/+53
| | | | | | | - Use -- when needed so Linux getopt(3) won't get confused. - Follow POSIX more closely. Submitted by: Szabolcs Szakacsits <szaka@ntfs-3g.org>
* fstest for Linux:pjd2008-11-231-2/+26
| | | | Automatically detect file system type.
* FreeBSD's way of handling rmdir("..") is not POSIX-compilant.pjd2008-11-231-9/+3
|
* Shorter version.pjd2008-11-231-14/+4
|
* Add support for pathconf(2).pjd2008-11-231-1/+57
|
* Detect operating system automatically.pjd2008-11-231-5/+21
|
* fstest for Linux:pjd2008-11-231-4/+27
| | | | | - Use /dev/urandom, it is more portable. - Implement todo() function which allows to mark known failures.
* IFp4: Regression tests for FreeBSD/ZFS chflags(2)/lchflags(2).pjd2008-11-2214-88/+136
|
* Update ZFS from version 6 to 13 and bring some FreeBSD-specific changes.pjd2008-11-1754-0/+12014
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This bring huge amount of changes, I'll enumerate only user-visible changes: - Delegated Administration Allows regular users to perform ZFS operations, like file system creation, snapshot creation, etc. - L2ARC Level 2 cache for ZFS - allows to use additional disks for cache. Huge performance improvements mostly for random read of mostly static content. - slog Allow to use additional disks for ZFS Intent Log to speed up operations like fsync(2). - vfs.zfs.super_owner Allows regular users to perform privileged operations on files stored on ZFS file systems owned by him. Very careful with this one. - chflags(2) Not all the flags are supported. This still needs work. - ZFSBoot Support to boot off of ZFS pool. Not finished, AFAIK. Submitted by: dfr - Snapshot properties - New failure modes Before if write requested failed, system paniced. Now one can select from one of three failure modes: - panic - panic on write error - wait - wait for disk to reappear - continue - serve read requests if possible, block write requests - Refquota, refreservation properties Just quota and reservation properties, but don't count space consumed by children file systems, clones and snapshots. - Sparse volumes ZVOLs that don't reserve space in the pool. - External attributes Compatible with extattr(2). - NFSv4-ACLs Not sure about the status, might not be complete yet. Submitted by: trasz - Creation-time properties - Regression tests for zpool(8) command. Obtained from: OpenSolaris
* Add a test for the "or more" part of the following POSIX specification.dds2008-11-112-1/+3
| | | | | | "A function can be preceded by one or more '!' characters, in which case the function shall be applied if the addresses do not select the pattern space."
* Make test for write access to the directory being moved a little moretrasz2008-11-071-5/+9
| | | | | | specific. Approved by: rwatson (mentor)
* Improve output when a test fails.trasz2008-11-071-2/+2
| | | | Approved by: rwatson (mentor)
* Change ZFS behaviour to match UFS: when moving (rename(2)) a subdirectorytrasz2008-11-061-0/+38
| | | | | | | from one parent directory to another, in addition to the usual access checks one also needs write access to the subdirectory being moved. Approved by: rwatson (mentor), pjd
* Implement support for RPCSEC_GSS authentication to both the NFS clientdfr2008-11-034-0/+725
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and server. This replaces the RPC implementation of the NFS client and server with the newer RPC implementation originally developed (actually ported from the userland sunrpc code) to support the NFS Lock Manager. I have tested this code extensively and I believe it is stable and that performance is at least equal to the legacy RPC implementation. The NFS code currently contains support for both the new RPC implementation and the older legacy implementation inherited from the original NFS codebase. The default is to use the new implementation - add the NFS_LEGACYRPC option to fall back to the old code. When I merge this support back to RELENG_7, I will probably change this so that users have to 'opt in' to get the new code. To use RPCSEC_GSS on either client or server, you must build a kernel which includes the KGSSAPI option and the crypto device. On the userland side, you must build at least a new libc, mountd, mount_nfs and gssd. You must install new versions of /etc/rc.d/gssd and /etc/rc.d/nfsd and add 'gssd_enable=YES' to /etc/rc.conf. As long as gssd is running, you should be able to mount an NFS filesystem from a server that requires RPCSEC_GSS authentication. The mount itself can happen without any kerberos credentials but all access to the filesystem will be denied unless the accessing user has a valid ticket file in the standard place (/tmp/krb5cc_<uid>). There is currently no support for situations where the ticket file is in a different place, such as when the user logged in via SSH and has delegated credentials from that login. This restriction is also present in Solaris and Linux. In theory, we could improve this in future, possibly using Brooks Davis' implementation of variant symlinks. Supporting RPCSEC_GSS on a server is nearly as simple. You must create service creds for the server in the form 'nfs/<fqdn>@<REALM>' and install them in /etc/krb5.keytab. The standard heimdal utility ktutil makes this fairly easy. After the service creds have been created, you can add a '-sec=krb5' option to /etc/exports and restart both mountd and nfsd. The only other difference an administrator should notice is that nfsd doesn't fork to create service threads any more. In normal operation, there will be two nfsd processes, one in userland waiting for TCP connections and one in the kernel handling requests. The latter process will create as many kthreads as required - these should be visible via 'top -H'. The code has some support for varying the number of service threads according to load but initially at least, nfsd uses a fixed number of threads according to the value supplied to its '-n' option. Sponsored by: Isilon Systems MFC after: 1 month
OpenPOWER on IntegriCloud