| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
about it.
|
|
|
|
| |
Reviewed by: phk
|
|
|
|
|
|
|
|
| |
FreeBSD, and makes ugly diffs with the other crt1.c's. Leave
behind a comment (words supplied by Thomas Moestl) that explain
the issue.
OK'ed by: tmm
|
|
|
|
| |
Reviewed by: jeff
|
|
|
|
|
|
| |
to fiddle the disk we can get away with it.
Try to use DIOCBSDBB to write boot code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
labeled disk.
This is complicated by the fact that BBSIZE is greater than the
PAGE_SIZE limit ioctl inflicts on arguments which are automatically
copied in.
As long as we don't need access to userland memory (copyin/out) we
can deal with the ioctl using g_callme() which executes it from the
GEOM event thread.
Once we need copyin/out, we need to return the bio with EDIRIOCTL
in order to make geom_dev call us back in the original process context
where copyin will work.
Unfortunately, that results in us getting called with Giant, so
we have to DROP_GIANT/PICKUP_GIANT around the code where we diddle
GEOMs internals.
Sometimes you just can't win...
... But it does make geom_bsd.c an almost complete example of the
GEOM beastiarium.
|
| |
|
|
|
|
|
| |
Make it compile for the SMP case..
statclock_process() has changed prototypes.
|
|
|
|
| |
Submitted by: Andreas Kohn <andreas.kohn@gmx.net> (via -STABLE)
|
| |
|
|
|
|
|
| |
PR: standards/45274
Submitted by: Craig Rodrigues <rodrigc@attbi.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
directory can be specified for a user or a group.
Add the manpage ftpchroot(5) since the file's format has grown
complex enough.
PR: bin/45327
Portions submitted by: Hideki SAKAMOTO <sakamoto@hlla.is.tsukuba.ac.jp>
MFC after: 1 week
|
|
|
|
| |
- remove unncessary descriptor updates.
|
|
|
|
|
|
| |
back.
Pointed out by: peter
|
|
|
|
|
| |
- Improve debug message for mbuf handling.
- Wait 1 sec for DMA stop in fwohci_i{t,r}x_disable() before freeing buffers.
|
|
|
|
|
|
|
|
| |
creates a single file named just "boot".
Apart from the fact that the option "-s" is now gone and that "-b" should
be pointed at /boot/boot instead of /boot/boot1, this patch should be
a no-op.
|
|
|
|
| |
bootstrap code for disklabel using architectures.
|
|
|
|
|
| |
and if we get such an architecture, we can just avoid using the relevant
options.
|
|
|
|
|
| |
There is little if any reason to treat the two components separately
and it will simplify disklabel(8) and libdisk if we didn't.
|
|
|
|
| |
Spotted by: tjr
|
|
|
|
| |
Remove yet a usage message about -N/-W
|
|
|
|
| |
Reviewed by: juli
|
| |
|
| |
|
| |
|
|
|
|
| |
so no hacks are needed.
|
|
|
|
| |
Rearrange bits in writelabel() a bit for improved readability.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
|
| |
|
| |
|
| |
|
|
|
|
| |
like this negated any practical value of the feature.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for the disklabel: This facility is OBE.
First of all, we cannot sensibly implement this in a properly stacked
environment.
Second, if we did, it would confuse the heck out of users who
wouldn't be able to "start from scratch" by dd(8)'ing /dev/zero
onto /dev/da0.
Third, the offered protection is not comprehensive: no other software
would respect it.
Fourth and finally, the disklabel is already protected against
tampering if it controls open partitions.
Uselessness of these options discussed with: peter
|
|
|
|
|
|
|
|
|
|
| |
a NULL filename argument allows a stream's mode to be changed. At the
moment it just recycles the old file descriptor instead of storing the
filename somewhere and using that to reopen the file, as the standard
seems to require. Strictly conforming C99 applications probably can't
tell the difference but POSIX ones can.
PR: 46791
|
|
|
|
|
|
| |
the correctness of this program. Previously, it printed out
the MD5 values of some test strings, but did not tell you
if they were correct or not!
|
|
|
|
|
| |
Pointy hat to: jeff
Spotted by: dillon
|
|
|
|
|
| |
Thanks to Bill Fenner for providing access to an e450, and to Tomi Vainio
for testing on an e3500 (any many other machines).
|
| |
|
| |
|
|
|
|
|
| |
of the scheduler.
- Add SCHED_4BSD as the scheduler for all kernel config files in cvs.
|
|
|
|
|
| |
scheduler with many SMP benefits. It is still very experimental and should
be used only in test environments.
|
| |
|
| |
|
|
|
|
| |
the user tlb fault handlers.
|
|
|
|
| |
entries to the SEE ALSO section.
|
|
|
|
|
|
|
| |
when -R is combined with patterns that might match ".." (like ".*").
PR: 46415
Submitted by: Gary W. Swearingen <swear@attbi.com>
|
|
|
|
| |
in the prom but no keyboard is plugged in.
|
|
|
|
|
|
|
|
|
|
|
| |
functions implemented approximately the same limits on fragment memory
usage, but in different fashions.)
End user visible changes:
- Fragment reassembly queues are freed in a FIFO manner when maxfragpackets
has been reached, rather than all reassembly stopping.
MFC after: 5 days
|
| |
|