| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
match the wildcard unit passed to BUS_ADD_CHILD().
|
| |
|
|
|
|
| |
This should fix the missed devices on some systems.
|
|
|
|
|
|
| |
remote CPU. While here, abstract thread suspension code into a function
called sig_suspend_threads, the function is called when a process received
a STOP signal.
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Suggested by: ru
MFC after: 3 days
|
| |
|
|
|
|
|
| |
to make kernel crash dumps to umass devices work, at least in some
cases.
|
|
|
|
|
|
|
|
|
|
|
| |
invalid in nd6_timer().
PR: kern/93170
Reported by: kris
Submitted by: JINMEI Tatuya <jinmei__at__isl.rdc.toshiba.co.jp>
Confirmed by: kris
Obtained from: KAME
MFC after: 2 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
v_vflags.
MFC after: 1 week
Submitted by: Antoine Brodin <antoine at brodin at laposte dot net>
|
|
|
|
|
|
|
| |
during suspend <-> resume and module load <-> unload.
PR: kern/92764
MFC after: 3 days
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Obtained from: TrustedBSD Project
|
|
|
|
|
|
| |
its pre-authentication children are covered by naflags.
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
| |
it and drop it afterwards.
Found by: kris
MFC after: 1 week
|
|
|
|
|
|
| |
in if.c). Count output errors.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
save the MCA state of the AP. Saving the MCA state of the AP requires
us to allocate memory, which uses sleep locks.
Now that we correct the spinlock nesting of the AP without having
schedlock, avoid calling spinlock_exit(). Instead call critical_exit()
and manually clear the MD spinlock count.
MFC after: 3 days
|
|
|
|
|
|
| |
memory statistics record stream via sysctl.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to preserve currect behaviour). When set to 0, components are not
disconnected - graid3 will try to still use them (only first error will
be logged). This is helpful when we have two broken components, but in
different places, so actually all data is available.
Such buggy component will be visible in 'graid3 list' output with flag
BROKEN.
- Never disconnect the last valid component. If we detect errors there we
will just pass them up. This wasn't reasonable to deny access to the
whole provider because of one broken sector.
Prodded by: ru
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to preserve currect behaviour). When set to 0, components are not
disconnected - gmirror will try to still use them (only first error will
be logged). This is helpful when we have two broken components, but in
different places, so actually all data is available.
Such buggy component will be visible in 'gmirror list' output with flag
BROKEN.
- Never disconnect the last valid component. If we detect errors there we
will just pass them up. This wasn't reasonable to deny access to the
whole provider because of one broken sector.
Prodded by: ru
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
kern.geom.raid3.idletime seconds. Write, not any requests.
Mark array as clean immediatelly on last write close.
Prodded by: ru
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
kern.geom.mirror.idletime seconds. Write, not any requests.
Mark array as clean immediatelly on last write close.
Prodded by: ru
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
An example entries for loader.conf to make it possible:
geli_da0_keyfile0_load="YES"
geli_da0_keyfile0_type="da0:geli_keyfile0"
geli_da0_keyfile0_name="/boot/keys/da0.key0"
geli_da0_keyfile1_load="YES"
geli_da0_keyfile1_type="da0:geli_keyfile1"
geli_da0_keyfile1_name="/boot/keys/da0.key1"
geli_da0_keyfile2_load="YES"
geli_da0_keyfile2_type="da0:geli_keyfile2"
geli_da0_keyfile2_name="/boot/keys/da0.key2"
geli_da1s3a_keyfile0_load="YES"
geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0"
geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key"
Thanks for jhb and kan who showed me the right direction.
MFC after: 3 days
|
|
|
|
|
|
| |
boot. Other methods just don't work properly.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Keep accounting time (in per-cpu) cputicks and the statistics counts
in the thread and summarize into struct proc when at context switch.
Don't reach across CPUs in calcru().
Add code to calibrate the top speed of cpu_tickrate() for variable
cpu_tick hardware (like TSC on power managed machines).
Don't enforce monotonicity (at least for now) in calcru. While the
calibrated cpu_tickrate ramps up it may not be true.
Use 27MHz counter on i386/Geode.
Use TSC on amd64 & i386 if present.
Use tick counter on sparc64
|
| |
|
| |
|
|
|
|
| |
I've had these improvements in my tree for almost a year now...
|
|
|
|
|
| |
effect and draw attention to the fact that the list has stronger ordering
requirements than before.
|
|
|
|
| |
now-redundant cast on establishing the interrupt.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
automatically both SATA and SAS drives. The async SAS event handling we catch
but ignore at present (so automagic attach/detach isn't hooked up yet).
Do 64 bit PCI support- we can now work on systems with > 4GB of memory.
Do large transfer support- we now can support up to reported chain depth, or
the length of our request area. We simply allocate additional request elements
when we would run out of room for chain lists.
Tested on Ultra320, FC and SAS controllers on AMD64 and i386 platforms.
There were no RAID cards available for me to regression test.
The error recovery for this driver still is pretty bad.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to work with ipmitools. It works with other tools that have an OpenIPMI
driver interface. The port will need to get updated to used this.
I have not implemented the IPMB mode yet so ioctl's for that don't
really do much otherwise it should work like the OpenIPMI version.
The ipmi.h definitions was derived from the ipmitool header file.
The bus attachments are done for smbios and pci/smbios. Differences
in bus probe order for modules/static are delt with. ACPI attachment
should be done.
This drivers registers with the watchdod(4) interface
Work to do:
- BT interface
- IPMB mode
This has been tested on Dell PE2850, PE2650 & PE850 with i386 & amd64
kernel.
I will link this into the build on next week.
Tom Rhodes, helped me with the man page.
Sponsored by: IronPort Systems Inc.
Inspired from: ipmitool & Linux
|
|
|
|
|
|
|
|
|
|
|
|
| |
o add dfs+radar hooks; DFS is presently disabled in the hal
o channel and mode handling changes
o various api changes
o be more aggressive about iq calibration settling so ap mode
operation is better immediately after startup
o rfkill/rfsilent sysctl support
o tpc ack/cts sysctl support
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
o new chip support
o new platforms: powerpc-be-elf, sparc64-be-elf, and alpha-elf
(alpha is untested, others are known to work)
o many fixes and improvements
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| | |
to an include file.
Reviewed by: imp
Approved by: imp (mentor)
|
| |
| |
| |
| |
| |
| |
| | |
RELENG_6, and would require a lower version number.
Requested by: glebius
Approved by: rwatson (mentor)
|
| |
| |
| |
| |
| |
| |
| |
| | |
always turning it on along with any flags set in the lower mount.
Tested by: kris
Reviewed by: jeff
MFC after: 3 days
|
| |
| |
| |
| | |
ping-pong on SMP.
|
| |
| |
| |
| |
| |
| |
| |
| | |
zero in this case.) A kernel driver has IFF_DRV_RUNNING
at its full disposal while IFF_UP may be toggled only by
humans or their daemonic deputies from the userland.
MFC after: 3 days
|
| |
| |
| |
| | |
is now fully stopped, this was already in kse_exit().
|
| |
| |
| |
| | |
MFC after: 2 weeks
|