| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
control over the result of buildworld and installworld; this especially
helps packaging systems such as nanobsd
Reviewed by: various (posted to arch)
MFC after: 1 month
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Because pseudo-terminal master file descriptors no longer have a vnode
underneath, we have to fill in fstat() values ourselves. Make our
implementation somewhat sane by returning the timestamps of the TTY
device node that corresponds with our file descriptor.
Obtained from: //depot/projects/mpsafettty/...
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the code to prevent useless waste of space.
- Remove support for quote bits. There is not a single driver that needs
these bits anymore. This means putc() now accepts a char instead of an
int.
- Remove the unneeded catq() and nextc() routines. They were only used
by the old TTY layer.
- Convert the clist code to use ANSI C prototypes.
|
|
|
|
|
| |
building multiple NanoBSD images at once to keep track of what is
running and what isn't.
|
|
|
|
|
|
|
|
| |
large number of physical pages.
PR: 126158
Submitted by: Dmitry Tejblum
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the MPSAFE TTY branch I noticed the vfs timestamps inside devfs were
allocated with 0, where the getattr() routine bumps the timestamps to
boottime if the value is below 3600. The reason why it has been designed
like this, is because timestamps during boot are likely to be invalid.
This means that device nodes that are created on demand (posix_openpt())
have timestamps with a value of boottime, which is not what we want.
Solve this by calling vfs_timestamp() inside devfs_alloc().
Discussed with: kib
|
| |
|
| |
|
|
|
|
|
| |
Approved by: julian (mentor)
MFC after: 3 days
|
| |
|
|
|
|
| |
as being unable to associate
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
script mode like the MRI(Microtec Research Inc.) "librarian" program.
Originally this option is provided by Binutils ar(1) to ease the
transition for developers who are used to writing "librarian" scripts.
We added this option to BSD ar(1) because:
1. Further improve the compatibility with Binutils ar(1).
2. There are still a few software using this -M option. (at least one
in our ports collection)
Suggested by: rink & erwin
|
|
|
|
|
|
| |
remove it from this man page.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
phase of establishing mapping.
Discussed with: rwatson, jhb, rnoland
Tested by: rnoland
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
initialize the vattr structure in VOP_GETATTR() with VATTR_NULL(),
vattr_null() or by zeroing it. Remove these to allow preinitialization
of fields work in vn_stat(). This is needed to get birthtime initialized
correctly.
Submitted by: Jaakko Heinonen <jh saunalahti fi>
Discussed on: freebsd-fs
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
NODEV is more appropriate when va_rdev doesn't have a meaningful value.
Submitted by: Jaakko Heinonen <jh saunalahti fi>
Suggested by: bde
Discussed on: freebsd-fs
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
| |
VOP_GETATTR() call in vn_stat(). Thus if a file system doesn't
initialize those fields in VOP_GETATTR() they will have a sane default
value.
Submitted by: Jaakko Heinonen <jh saunalahti fi>
Discussed on: freebsd-fs
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
| |
initialize va_vaflags and va_spare because they are not part of the
VOP_GETATTR() API. Also don't initialize birthtime to ctime or zero.
Submitted by: Jaakko Heinonen <jh saunalahti fi>
Reviewed by: bde
Discussed on: freebsd-fs
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
| |
returning uninitialized birthtime. Most file systems don't initialize
birthtime properly in their VOP_GETTATTR().
Submitted by: Jaakko Heinonen <jh saunalahti fi>
Reviewed by: bde
Discussed on: freebsd-fs
MFC after: 1 month
|
|
|
|
|
|
| |
the ifnet from cloner's list. Expose if_clone_destroyif api to do this.
Submitted by: sam
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reverse the direction of pmap_promote_pde()'s traversal over the specified
page table page. The direction of the traversal can matter if
pmap_promote_pde() has to remove write access (PG_RW) from a PTE that
hasn't been modified (PG_M). In general, if there are two or more such
PTEs to choose among, it is better to write protect the one nearer the
high end of the page table page rather than the low end. This is because
most programs access memory in an ascending direction. The net result of
this change is a sometimes significant reduction in the number of failed
promotion attempts and the number of pages that are write protected by
pmap_promote_pde().
MFamd64 SVN rev 179777 CVS rev 1.621
Tweak the promotion test in pmap_promote_pde(). Specifically, test PG_A
before PG_M. This sometimes prevents unnecessary removal of write access
from a PTE. Overall, the net result is fewer demotions and promotion
failures.
|
| |
|
|
|
|
| |
MFC after: 1 month
|
| |
|
| |
|
|
|
|
|
|
| |
compile these with -mcpu=ultrasparc (which is the hard-coded default
of our system compiler), which allows the remainder of the kernel to
be compiled with "only" -mcpu=v9 for reference and testing purposes.
|
|
|
|
|
|
|
|
|
|
| |
consists of CPUs running at different speeds, for driving hardclock as
these timers in turn are driven at frequencies as low as 5MHz, resulting
in bad granularity compared to the TICK timers. However, don't employ
the workaround for the BlackBird erratum #1 when using the TICK timer
on machines with cheetah-class CPUs for performance reasons.
Reported by: Florian Smeets
|
|
|
|
|
|
|
|
|
| |
net/route.h, because the vnet code will need those constants as
well.
Reviewed by: bz
Approved by: julian (mentor)
MFC after: never
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
of "cd:,\\:tbxi" with properly configured boot.tbxi, instead of booting
\boot\loader directly. Rev 183168 could probably stay, since it can be
viewed as an anti-foot-shooting measure and has no impact on normal
operation. I can revert it as well, if anybody objects.
|
| |
|
|
|
|
|
|
|
|
| |
functions used by other code in the tree. As such it was removed from
the merged tree until the functions were needed in the future. The
file was missing from the FreeBSD import, but it was listed in the
files.mips file as being standard. Remove it from there until such
time as we need one.
|
|
|
|
| |
omit it like we do for arm.
|
|
|
|
|
|
|
| |
to vga_pci.c to request on behalf of it's children. This causes vgapci to show
up as the interrupt owner in vmstat -i, rather than the child device.
Approved by: jhb(mentor)
|
| |
|
|
|
|
|
|
|
| |
into FBSD_1.1 section where they should be.
Pointed out by: kib, deischen
MFC after: 3 days
|
|
|
|
|
|
| |
clarity.
Suggested by: dougb
|
|
|
|
|
|
| |
Submitted by: jhb
Tested by: olli
MFC after: 3 days
|
| |
|
|
|
|
| |
(and quiet some compiler warnings for vfs_donmount)
|
| |
|
| |
|
|
|
|
| |
measurements.
|