| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
unconditionally on amd64. On i386, we assume PAT is usable if the CPU
vendor is not Intel or CPU model is newer than Pentium IV.
Reviewed by: alc, jhb
|
|
|
|
|
|
|
|
| |
Unlike with SCHED_BSD, however, it can only be set to 0 at boot time,
it's not possible to change it at runtime.
Reviewed by: jhb
MFC after: 1 month
|
| |
|
|
|
|
| |
move to the new usb stack are in progress.
|
|
|
|
| |
naming). The old usb stack can be compiled in my prefixing the name with 'o'.
|
|
|
|
| |
Submitted by: bde (partly)
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
different cpu is still assigned to that vector by never clearing idt
entries. This was only provided as a debugging feature and the bugs
are caught by other means.
- Drop the sched lock when rebinding to reassign an interrupt vector
to a new cpu so that pending interrupts have a chance to be delivered
before removing the old vector.
Discussed with: tegge, jhb
|
|
|
|
|
| |
Submitted by: Takahiro Kurosawa <takahiro.kurosawa gmail com>
PR: kern/131506
|
|
|
|
| |
Reminded by: Michael Butler
|
|
|
|
| |
Tested by: make universe
|
|
|
|
|
|
|
| |
vm_page_wakeup(). (This change is applicable to RELENG_7 but not
RELENG_6.)
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
| |
the same dma tag. However, it can happen multiple dma tags share the same
bounce zone too, so add a per-bounce zone map counter, and check it instead of
the dma tag map counter, to know if we have to alloc more pages.
Reported by: miwi
Reviewed by: scottl
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
offset. This is needed for the ehci hardware buffer rings that assume
this behavior.
This is an interim solution, and a more general one is being worked
on. This solution doesn't break anything that doesn't ask for it
directly. The mbuf and uio variants with this flag likely don't work
and haven't been tested.
Universe builds with these changes. I don't have a huge-memory
machine to test these changes with, but will be happy to work with
folks that do and hps if this changes turns out not to be sufficient.
Submitted by: alfred@ from Hans Peter Selasky's original
|
| |
|
|
|
|
| |
protptyoes for the legacy_* impelemtnations of these kobj methods.
|
|
|
|
|
|
|
|
|
|
| |
- remove misleading nve/nfe comments, which make it hard to
distinguish those two at a first glance
- bring pbio documentation to the block comment together with
other drivers
I also brought commented out line responsible for si(4), since it
seems to compile and already has respective comment in this file.
|
|
|
|
|
|
|
|
|
| |
need to explicitly list it here once again. This removes:
WARNING: duplicate option `DEV_URAL' encountered.
WARNING: duplicate device `ural' encountered.
Warnings when compiling LINT on amd64.
|
|
|
|
|
|
|
|
|
|
|
|
| |
- correct format strings
- fill opt_agp.h if AGP_DEBUG is defined
- bring AGP_DEBUG to LINT by mentioning it in NOTES
This should hopefully fix a warning that was...
Found by: Coverity Prevent(tm)
CID: 3676
Tested on: amd64, i386
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
mode.
- Make the NMI handler run on its own stack (TSS_IST2).
- Store the GSBASE value for each CPU just before the start of
each NMI stack, permitting efficient retrieval using %rsp-relative
addressing.
- For NMIs taken from kernel mode, program MSR_GSBASE explicitly
since one or both of MSR_GSBASE and MSR_KGSBASE can be potentially
invalid. The current contents of MSR_GSBASE are saved and restored
at exit.
- For NMIs handled from user mode, continue to use 'swapgs' to
load the per-CPU GSBASE.
Reviewed by: jeff
Debugging help: jeff
Tested by: gnn, Artem Belevich <artemb at gmail dot com>
|
|
|
|
| |
Noticed by: bde
|
|
|
|
|
|
| |
for moving between a segment register and a 32-bit memory location.
Looked at by: jhb
|
|
|
|
|
|
|
|
| |
more irqs as we have more cpus. This is principally useful on systems
with msi devices which may want many irqs per-cpu.
Discussed with: jhb
Sponsored by: Nokia
|
|
|
|
|
|
|
|
| |
32-bit processes. The value matches the initial setting used by
FreeBSD/i386. Otherwise, 32-bit binaries using floating point would use
a slightly different initial state when run on FreeBSD/amd64.
MFC after: 1 week
|
|
|
|
|
| |
whether TSC is P-state invariant or not. In fact, this MSR is writable but
we just leave it at the BIOS default for now.
|
|
|
|
|
|
|
|
|
|
|
| |
the fsbase value. The switch loads the fs segment register, that
invalidates the value in fsbase msr, thus value in %r9 can not be
considered the current value for fsbase anymore.
Unconditionally reload fsbase when switching to 32bit binary.
PR: 130526
MFC after: 3 weeks
|
|
|
|
| |
Suggested by: phk, luigi
|
|
|
|
|
| |
Pointy hat to: myself
Submitted by: scottl
|
| |
|
| |
|
|
|
|
|
|
| |
there is no particular reason for them to be i386-only.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
Otherwise, interrupt may happen while we run with kernel CS and usermode
gsbase.
Reviewed by: jeff
MFC after: 1 week
|
|
|
|
|
|
| |
Add USB scanner support to USB2 config files.
Submitted by: Hans Petter Selasky
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- add a reference to the config(5) manpage;
- hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not
in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..)
and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or
create a new kernel config, so having the suggestion there is
more effective.
I am only touching i386 and amd64 because the other GENERIC files
are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
| |
to GENERIC configuration files. This brings what's in 8.x in sync
with what is in 7.x, but does not change any current defaults.
Possibly they should now be enabled in head by default?
|
|
|
|
| |
compile).
|
|
|
|
|
|
| |
USBng.
If it makes sense, it could be done for arm/mips too.
|
|
|
|
|
|
|
| |
Both ia64 and powerpc were using gpart exclusively already
so there's no change for those two.
Discussed on: arch@
|
|
|
|
| |
Reviewed by: peter
|
|
|
|
|
|
| |
in the first place, let alone migrated to linux emulation.
Reviewed by: peter, rdivacky
|
|
|
|
| |
path.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
time it is marked for user space callchain capture in the NMI
handler and the time the callchain capture callback runs.
- Improve code and control flow clarity by invoking hwpmc(4)'s user
space callchain capture callback directly from low-level code.
Reviewed by: jhb (kern/subr_trap.c)
Testing (various patch revisions): gnn,
Fabien Thomas <fabien dot thomas at netasq dot com>,
Artem Belevich <artemb at gmail dot com>
|
| |
|
| |
|
|
|
|
| |
routine to read it.
|
|
|
|
|
|
|
| |
promotion to "on".
Reminded by: jhb
Tested by: kris
|