Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2 |
|
#
fcf6efef |
| 02-Mar-2019 |
Sascha Wildner <saw@online.de> |
kernel: Remove numerous #include <sys/thread2.h>.
Most of them were added when we converted spl*() calls to crit_enter()/crit_exit(), almost 14 years ago. We can now remove a good chunk of them agai
kernel: Remove numerous #include <sys/thread2.h>.
Most of them were added when we converted spl*() calls to crit_enter()/crit_exit(), almost 14 years ago. We can now remove a good chunk of them again for where crit_*() are no longer used.
I had to adjust some files that were relying on thread2.h or headers that it includes coming in via other headers that it was removed from.
show more ...
|
Revision tags: v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0 |
|
#
ba87a4ab |
| 24-Aug-2014 |
Sascha Wildner <saw@online.de> |
kernel/spinlock: Add a description to struct spinlock.
And add it to spin_init() and SPINLOCK_INITIALIZER().
Submitted-by: dclink (see <http://bugs.dragonflybsd.org/issues/2714>) OK'd-by: dill
kernel/spinlock: Add a description to struct spinlock.
And add it to spin_init() and SPINLOCK_INITIALIZER().
Submitted-by: dclink (see <http://bugs.dragonflybsd.org/issues/2714>) OK'd-by: dillon
show more ...
|
Revision tags: v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3 |
|
#
aaa57655 |
| 17-Aug-2012 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
pci: Enable PCIe memory mapped configuration again
bd7ad9e91e71693907a00c74ab8dfc457cd655c9 should have fixed the system hanging seen by y0netan1@
|
#
8848f797 |
| 26-May-2012 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
pci: Disable PCI express memory mapped access method by default
It seems to hang some systems during boot.
Reported-by: y0netan1@
|
#
f018bb2e |
| 25-May-2012 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
pci: Print PCIe memory mapped accessing information a little bit earlier
|
#
926777f6 |
| 14-May-2012 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
pci: Support PCI Express Configuration Space memory-mapped access mechanism
Also remove the outdated type 2 Configuration Space access mechanism; it should never been seen on platforms w/ AMD64 capa
pci: Support PCI Express Configuration Space memory-mapped access mechanism
Also remove the outdated type 2 Configuration Space access mechanism; it should never been seen on platforms w/ AMD64 capable CPUs.
Obtained-from: FreeBSD
show more ...
|
Revision tags: v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
#
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather than continuing to create new binutils branches for each new version.
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0 |
|
#
4ea06a72 |
| 01-Nov-2009 |
Alexander Polakov <polachok@gmail.com> |
Expand the support for PCI-e memory mapped configuration space access.
This defaults to off and must be explicitly enabled by setting the loader tunable hw.pci.mcfg=1. - Add support for the Intel 91
Expand the support for PCI-e memory mapped configuration space access.
This defaults to off and must be explicitly enabled by setting the loader tunable hw.pci.mcfg=1. - Add support for the Intel 915GM chipsets by reading the BAR. - Add parsing of the ACPI MCFG table to discover memory mapped configuration access on modern machines. - For config requests to busses not listed in ACPI's min/max valid buses, fall back to using type #1 configuration access instead. - Add a workaround for some K8 chipsets that do not expose all devices on bus 0 via MCFG and fall back to type #1 for those devices instead.
Obtained-from: FreeBSD
show more ...
|
#
b2b3ffcd |
| 04-Nov-2009 |
Simon Schubert <corecode@dragonflybsd.org> |
rename amd64 architecture to x86_64
The rest of the world seems to call amd64 x86_64. Bite the bullet and rename all of the architecture files and references. This will hopefully make pkgsrc build
rename amd64 architecture to x86_64
The rest of the world seems to call amd64 x86_64. Bite the bullet and rename all of the architecture files and references. This will hopefully make pkgsrc builds less painful.
Discussed-with: dillon@
show more ...
|
#
c1543a89 |
| 04-Nov-2009 |
Simon Schubert <corecode@dragonflybsd.org> |
rename amd64 architecture to x86_64
The rest of the world seems to call amd64 x86_64. Bite the bullet and rename all of the architecture files and references. This will hopefully make pkgsrc build
rename amd64 architecture to x86_64
The rest of the world seems to call amd64 x86_64. Bite the bullet and rename all of the architecture files and references. This will hopefully make pkgsrc builds less painful.
Discussed-with: dillon@
show more ...
|
#
287a8577 |
| 30-Aug-2010 |
Alex Hornung <ahornung@gmail.com> |
spinlocks - Rename API to spin_{try,un,}lock
* Rename the API to spin_trylock, spin_unlock and spin_lock instead of spin_lock_wr, spin_unlock_wr and spin_trylock_wr now that we only have exclusi
spinlocks - Rename API to spin_{try,un,}lock
* Rename the API to spin_trylock, spin_unlock and spin_lock instead of spin_lock_wr, spin_unlock_wr and spin_trylock_wr now that we only have exclusive spinlocks.
* 99% of this patch was generated by a semantic coccinelle patch
show more ...
|
#
9388fcaa |
| 04-Mar-2010 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - pmap (i386) - Reduce kmem use for foreign pmap mapping
* We've been having problems running out of KVA on i386 systems due to numerous reasons. KVA use by the kernel is just too tight.
kernel - pmap (i386) - Reduce kmem use for foreign pmap mapping
* We've been having problems running out of KVA on i386 systems due to numerous reasons. KVA use by the kernel is just too tight.
* Reserve space for foreign pmap page table mappings on a cpu-by-cpu basis instead of for SMP_MAXCPU. This reduces KVM use from 68MB to (ncpu*4MB). Use the APT entry for cpu0 and use kmem_alloc_nofault() for the APs.
This frees up 52MB of KVA which doesn't sound like a lot but actually is.
* Add an alignment argument to kmem_alloc_nofault() and vm_map_find().
* vm_map_findspace() already had an alignment argument, but adjust the value passed to be at least PAGE_SIZE (this has no operational effect but is more correct).
show more ...
|