summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Change vn_start_write() to clear *mpp on all failures when non-NULL vpkib2008-10-211-1/+10
| | | | | | | | is supplied, since vm_pageout_scan() expects it to be cleared on error. Submitted by: tegge PR: 123768 MFC after: 1 week
* Hook in ipi handlerskmacy2008-10-211-20/+18
|
* remove gratuitous XEN definekmacy2008-10-211-8/+0
|
* don't globally define ipi_bitmap_handler on xenkmacy2008-10-212-1/+4
|
* Implement infrastructure for gluing i386 ipi functions in to xen's ↵kmacy2008-10-212-29/+151
| | | | infrastructure
* Add routine for initializing AP clockkmacy2008-10-211-16/+17
|
* Header cleanups and addition of IPI declarations for xenkmacy2008-10-216-32/+40
|
* Fix 'kern.timeconter.invariant_tsc' tunable and back out a redundant hack.jkim2008-10-211-4/+4
| | | | Somehow incomplete version was committed. :-(
* Remove unused age_txdqkevlo2008-10-211-2/+0
|
* No need to sync descriptors twice in age_rxintr()kevlo2008-10-211-6/+0
|
* Do not use PowerNow! if FID or VID is missing.jkim2008-10-211-1/+1
|
* Use power management information for AMD CPUs from identcpu.c.jkim2008-10-211-17/+1
|
* Turn off CPU frequency change notifiers when the TSC is P-state invariantjkim2008-10-219-18/+68
| | | | | or it is forced by setting 'kern.timecounter.invariant_tsc' tunable to non-zero.
* Detect Advanced Power Management Information for AMD CPUs.jkim2008-10-218-0/+38
|
* Bump __FreeBSD_version in order to reflect prototipes changes for theseattilio2008-10-201-1/+1
| | | | | | | | | | following functions: - bufobj_invalbuf() - bufsync() - vinvalbuf() - g_vfs_close and virtual function BO_SYNC().
* In the actual code for witness_warn:attilio2008-10-201-19/+12
| | | | | | | | | | - If there aren't spinlocks held, but there are problems with old sleeplocks, they are not reported. - If the spinlock found is not the only one, problems are not reported. Fix these 2 problems. Reported by: tegge
* Update a comment which to my reading had been misplaced in rev. 1.12bz2008-10-201-2/+3
| | | | | | | | | already (but probably had been way above as the code was there twice) and describe what was last changed in rev. 1.199 there (which now is in sync with in6_src.c r184096). Pointed at by: mlaier MFC after: 2 mmonths
* Bring over the change switching from using sequential to randombz2008-10-202-47/+55
| | | | | | | | | | | ephemeral port allocation as implemented in netinet/in_pcb.c rev. 1.143 (initially from OpenBSD) and follow-up commits during the last four and a half years including rev. 1.157, 1.162 and 1.199. This now is relying on the same infrastructure as has been implemented in in_pcb.c since rev. 1.199. Reviewed by: silby, rpaulo, mlaier MFC after: 2 months
* Make HDA PCM device boot and sndstat messages more alike to PCI device ones.mav2008-10-201-5/+21
| | | | | Move codec # out of the device name as it is a device address and not part of device type name.
* Tune boot messages a bit.mav2008-10-201-4/+4
| | | | Use <> brackets only at device name line.
* Assert that v_holdcnt is non-zero before entering lockmgr in vn_lockkib2008-10-202-0/+8
| | | | | | | | | and ffs_lock. This cannot catch situations where holdcnt is incremented not by curthread, but I think it is useful. Reviewed by: tegge, attilio Tested by: pho MFC after: 2 weeks
* In vfs_busy(), lockmgr() cannot legitimately sleep, because code checkedkib2008-10-201-1/+1
| | | | | | | | | | MNTK_UNMOUNT before, and mnt_mtx is used as interlock. vfs_busy() always tries to obtain a shared lock on mnt_lock, the other user is unmount who tries to drain it, setting MNTK_UNMOUNT before. Reviewed by: tegge, attilio Tested by: pho MFC after: 2 weeks
* Import interrupt management defines from latest xenlinuxkmacy2008-10-201-12/+28
|
* The active and bootable flags are not part of the type.marcel2008-10-201-11/+82
| | | | | | | | | | Export the active and bootable flags as attributes in the configuration XML and allow them to be manipulated with the set/unset commands. Since libdisk treats the flags as part of the partition type, preserve behavior by keeping them included in the configuration text.
* In realtimer_delete(), clear timer's value and interval to telldavidxu2008-10-201-0/+8
| | | | | | | realtimer_expire() to not rearm the timer, otherwise there is a chance that a callout will be left there and be tiggered in future unexpectly. Bug reported by: tegge@
* fix static key wep; r183248 caused drivers to be called for keys to besam2008-10-191-1/+2
| | | | | assigned to slots in the global key table but ath_key_alloc was not updated to handle that
* Atomically increment the number of awoken APs as all APs willmarcel2008-10-191-1/+1
| | | | | | be unleashed here. Pointed out by: christian.kandeler@hob.de
* Ktr(9) stores format string and arguments in the event circular buffer,kib2008-10-191-21/+25
| | | | | | | | | | | | not the string formatted at the time of CTRX() call. Stack_ktr(9) uses an on-stack buffer for the symbol name, that is supplied as an argument to ktr. As result, stack_ktr() traces show garbage or cause page faults. Fix stack_ktr() by using pointer to module symbol table that is supposed to have a longer lifetime. Tested by: pho MFC after: 1 week
* Correctly fill siginfo for the signals delivered by linux tkill/tgkill.kib2008-10-196-53/+132
| | | | | | | | | | | | | | | | | | | | | It is required for async cancellation to work. Fix PROC_LOCK leak in linux_tgkill when signal delivery attempt is made to not linux process. Do not call em_find(p, ...) with p unlocked. Move common code for linux_tkill() and linux_tgkill() into linux_do_tkill(). Change linux siginfo_t definition to match actual linux one. Extend uid fields to 4 bytes from 2. The extension does not change structure layout and is binary compatible with previous definition, because i386 is little endian, and each uid field has 2 byte padding after it. Reported by: Nicolas Joly <njoly pasteur fr> Submitted by: dchangin MFC after: 1 month
* - Forward port flush of page table updates on context switch or userretkmacy2008-10-193-2/+25
| | | | - Forward port vfork XEN hack
* GC gratuitous XEN defineskmacy2008-10-191-6/+0
|
* - move gdt, ldt allocation to before KPT allocationkmacy2008-10-192-42/+65
| | | | | | | | | - fix bugs where we would: - try to map the hypervisors address space - accidentally kick out an existing kernel mapping for some domain creation memory allocation sizes - accidentally skip a 2MB kernel mapping for some domain creation memory allocation sizes - don't rely on trapping in to xen to read rcr2, reference through vcpu - whitespace cleanups
* GC unused valueskmacy2008-10-192-13/+0
|
* Coalesce sequentional BIO_DELETE requests to slightly relax size and alignmentmav2008-10-181-8/+23
| | | | constraints required by the card.
* Implement BIO_DELETE command with MMC and SD erase commands.mav2008-10-184-149/+333
| | | | | | | | | | | | | | | | | Erase operation gives card's logic information about unused areas to help it implement wear-leveling with lower overhead comparing to usual writing. Erase is much faster then write and does not depends on data bus speed. Also as result of hitting in-card write logic optimizations I have measured up to 50% performance boost on writing undersized blocks into preerased areas. At the same time there are strict limitations on size and allignment of erase operations. We can erase only blocks aligned to the erase sector size and with size multiple of it. Different cards has different erase sector size which usually varies from 64KB to 4MB. SD cards actually allow to erase smaller blocks, but it is much more expensive as it is implemented via read-erase-write sequence and so not sutable for the BIO_DELETE purposes. Reviewed by: imp@
* The flags value was not always being copied out in the recv routine like itrrs2008-10-181-2/+3
| | | | | should be. Obtained from: Michael Tuexen
* New sockets (accepted) were not inheriting the proper snd/rcv buffer value.rrs2008-10-181-3/+5
| | | | Obtained from: Michael Tuexen
* - Peers rwnd is now available for the MIB.rrs2008-10-182-0/+2
| | | | Obtained from: Michael Tuexen
* - Adapt layer indication was always being given (it should onlyrrs2008-10-181-33/+28
| | | | | | | | | | be given when the user has enabled it). (Michael Tuexen) - Sack Immediately was not being set properly on the actual chunk, it was only put in the rcvd_flags which is incorrect. (Michael Tuexen) - added an ifndef userspace to one of the already present macro's for inet (Brad Penoff) Obtained from: Michael Tuexen and Brad Penoff MFC after: 4 weeks
* Reported by Yehuda Weinraub (yehudasa@gamil.com) - CRC32C algorithmrrs2008-10-181-3/+3
| | | | | | | | uses incorrect init_bytes value. It SHOULD have the number of bytes to get to a 4 byte boundary. PR: 128134 MFC after: 4 weeks
* Set PCB_32BIT and clear PCB_GS32BIT for linux32 binaries.kib2008-10-181-1/+2
| | | | | Tested by: dchagin MFC after: 3 days
* Add cr_canseeinpcb() doing checks using the cached socketbz2008-10-176-11/+44
| | | | | | | | | | credentials from inp_cred which is also available after the socket is gone. Switch cr_canseesocket consumers to cr_canseeinpcb. This removes an extra acquisition of the socket lock. Reviewed by: rwatson MFC after: 3 months (set timer; decide then)
* - For chipsets that can't do 64k transfers, fall back to 32k transfersjhb2008-10-174-5/+5
| | | | | | | | | | | | | (still a power of 2) rather than 63k transfers. Even with 63k transfers some machines (such as Dell SC1435's) were experiencing chronic data corruption. - Use the MIO method to talk to the Serverworks HT1000_S1 SATA controller like all the other SATA controllers rather than the compat PATA method. This lets the controller see all 4 SATA ports and also matches the behavior of the Linux driver. Silence from: sos MFC after: 3 days
* Add a mac_inpcb_check_visible implementation to all MAC policiesbz2008-10-177-0/+111
| | | | | | | that handle mac_socket_check_visible. Reviewed by: rwatson MFC after: 3 months (set timer; decide then)
* Wireless Mouse device of Sony VGP-WRC1 mouse/keyboard receiver has thebrooks2008-10-172-0/+3
| | | | | | | | same program interface as Microsoft Wireless Notebook Optical Mouse and needs a quirk. PR: usb/122712 MFC after: 3 days
* Add mac_inpcb_check_visible MAC Framework entry point, which is similarbz2008-10-173-0/+16
| | | | | | | to mac_socket_check_visible but operates on the inpcb. Reviewed by: rwatson MFC after: 3 months (set timer, decide then)
* Use the label from the socket credential rather than thebz2008-10-171-1/+2
| | | | | | | | solabel which was not set by the mac_partition policy. Spotted by: rwatson Reviewed by: rwatson MFC after: 3 days
* Track number of packets transmitted and number of packets receivedkmacy2008-10-171-1/+6
| | | | | PR: 125806 MFC after: 3 days
* Some 88E1149 PHY's page select is initialized to point to otheryongari2008-10-171-0/+14
| | | | | | | | | | | | | | | | | | | | bank instead of copper/fiber bank which in turn resulted in wrong registers were accessed during PHY operation. It is believed that page 0 should be used for copper PHY so reinitialize E1000_EADR to select default copper PHY. This fixes link establishment issue of nfe(4) on Sun Fire X4140. OpenBSD also has similimar patch but they just reset the E1000_EADR register to page 0. However some Marvell PHYs((88E3082, 88E1000) don't have the extended address register and the meaning of the register is quite different for each PHY model. So selecting copper PHY is limited to 88E1149 PHY which seems to be the only one that exhibits link establishment problem. If parent device know the type of PHY(either copper or fiber) that information should be notified to PHY driver but there is no good way to pass this information yet. Reported by: thompsa Reviewed by: thompsa
* make sure that SO_NO_DDP and SO_NO_OFFLOAD get passed in correctlykmacy2008-10-171-0/+2
| | | | | PR: 127360 MFC after: 3 days
OpenPOWER on IntegriCloud