| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
They were an ugly, gross hack.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
transfer to a malloc'd buffer and use that bufer for the ktrace event.
This means that genio ktrace events no longer need to be synchronous.
- Now that ktr_buffer isn't overloaded to sometimes point to a cached uio
pointer for genio requests and always points to a malloc'd buffer if not
NULL, free the buffer in ktr_freerequest() instead of in
ktr_writerequest(). This closes a memory leak for ktrace events that
used a malloc'd buffer that had their vnode ripped out from under them
while they were on the todo list.
Suggested by: bde (1, in principle)
|
|
|
|
|
|
|
|
| |
- Rename kern.ktrace_request_pool tunable/sysctl to
kern.ktrace.request_pool.
- Add a variable to control the max amount of data to log for genio events.
This variable is tunable via the tunable/sysctl kern.ktrace.genio_size
and defaults to one page.
|
|
|
|
|
| |
obtaining a ktr_request structure from the free pool so we can avoid
starving other threads of ktr_request structures.
|
|
|
|
| |
(ie: These files are long since obsolete)
|
| |
|
|
|
|
|
|
|
|
| |
and __stop_set_* became friendlier. This trick to force the export
of the section delimiter symbols is no longer necessary. We needed to
force this so that we could look up the symbols via a symbol table search
when the module was loaded at run time. ld used to eliminate them if
they were not referenced at compile/link time.
|
|
|
|
|
|
| |
bcopy/memcpy) seperately.
Submitted by: bde
|
|
|
|
| |
Submitted by: Eagle-eyes evans <bde@freebsd.org>
|
|
|
|
|
|
|
| |
the timestamp was aligned. ie: Use a void * instead of struct timeval *
which gcc assumes will be aligned. Go back to memcpy().
Submitted by: bde
|
|
|
|
|
|
|
| |
build this several times, and even tested loaded the module. I must have
changed something right before commit.
Pointed out by: bde
|
|
|
|
| |
tabs not spaces.
|
|
|
|
|
| |
Applications can not do this themselves, as the descriptors are hidden
behind the opaque `kvm_t' type.
|
|
|
|
| |
no-op. I assume it was meant that the close-on-exec flag be set here.
|
|
|
|
|
|
| |
this case, ugly macros, but the data tables can be reused:
Put one copy of the software HDLC tables in its own file.
|
|
|
|
| |
Bertrand Russell quotations.
|
|
|
|
| |
reverted out your change but hopefully that's it..
|
|
|
|
|
| |
I think it was a part of someone else's commit that
somehow got reverted by my patch.
|
| |
|
| |
|
|
|
|
| |
Reviewed by: davidxu@freebsd.org
|
|
|
|
|
|
|
| |
<sys/malloc.h>.
Sorted includes as much as possible. Removed banal comment(s) attached to
includes.
|
|
|
|
|
|
| |
i386/conf/NOTES rather than the global conf/NOTES.
Suggested by: bde
|
| |
|
|
|
|
| |
with. Enable `restrict' type-qualifier.
|
| |
|
|
|
|
| |
size_t. Add a new variable to cope.
|
| |
|
|
|
|
| |
Reviewed by: jhb, mdodd
|
|
|
|
| |
own patches as well as I should.
|
| |
|
|
|
|
|
|
| |
them when it's done.
Reviewed by: archie
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
| |
mode, and be more accurate about identifying begin lines so that spurious
ones don't have to be manually edited out, and be more forgiving about
errors so that -c mode is more useful.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
o Space used instead of a tab after `#define' and `typedef'.
o Sentences not ended with a period.
o Unaligned function names and other spacing issues.
|
| |
|
|
|
|
|
|
| |
hard-coding /dev/stdout as a special case.
Suggested by: jmallett
|
| |
|
|
|
|
| |
primitives.
|
| |
|
|
|
|
|
|
| |
It seems counter-intuitive that all drivers have to do this.
Pointed in right direction by: gj
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and adjacent tokens in declarations.
The added text was originally a single sentence I wrote and which
was heavily modified and extended by Bruce Evans.
This clarification attempt originates from differing usage of the
'restrict' type-qualifier.
Although various documents documents dicussing the C Programming
Language put a space between an asterisk and the 'restrict' keyword,
including the C99 standard (at least the n869.txt draft) and other
ISO/IEC JTC1/SC22/WG14 documents, the IEEE Std 1003.1-2001 document
does not separate them.
Discussed with: bde
Requested by: tjr
Separation using a single space also liked by: mike
|
|
|
|
|
|
|
|
|
|
|
| |
is a symbolic link in the PATH pointing back to /usr/bin/perl.
Change WARNS from 6 to 5 to account for the fact that sys/time.h,
included from sys/stat.h, produces a warning when compiled with
-pedantic.
PR: bin/42418
Reviewed by: roberto
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- use `struct uma_zone *' instead of uma_zone_t, so that <sys/uma.h> isn't
a prerequisite.
- don't include <sys/uma.h>.
Namespace pollution makes "opaque" types like uma_zone_t perfectly
non-opaque. Such types should never be used (see style(9)).
"Fixed" subsequently grown dependencies of this header on its own
pollution by polluting explicitly:
- include <sys/mutex.h> and its prerequisite <sys/lock.h> instead of
depending on namespace pollution 2 layers deep in <sys/uma.h>.
|