Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
program could force a copyin/copyout from/to memory mapped through the GTT,
forcing a "locking against myself" panic. The intel-gpu-tools "package" has
a test for this. The problem can be circumvented by making the fault handler
fail if we already hold the (DRM) lock. This will make the copyin/copyout
return with EFAULT making the caller fall back on a "slow path".
This makes it obvious that using a shared (read) lock here doesn't make any
sense. So use an exclusive (write) lock like everywhere else in the inteldrm
code.
|
|
|
|
|
|
Still a work-in-progress, but functional enough to work with both
Google Compute Engine and RHEVM. Committing so additional testing and
cleanup can be handled in tree.
thx Jiri B for RHEVM testing
ok dlg, deraadt
|
|
return values. Fixes at least one bug where userland would see a negative
errno value and hopefully doesn't introduce any new ones.
|
|
unsupported frame buffer configuration is requested.
|
|
more cache coherency issues, hopefully reducing the number of artifacts
showing up the screen.
|
|
|
|
Simplifies things a bit and reduces the diffs with Linux a bit too.
|
|
|
|
all by itself.
|
|
|
|
|
|
ok kettenis@
|
|
bring the interface out of all multicast mode once a range of multicast
addresses has been found.
Tested with QEMU and VMware's pcn(4) emulated adapters.
|
|
avoid the negative timeout panic and make __wait_seqno() properly wait
forever if no timeout was specified.
|
|
inteldrm(4) manages the GTT by itself.
ok miod@
|
|
flushes individual cache lines when needed.
|
|
|
|
ok jsg@
|
|
- Remove the maximum DMA segments handling bits as it is unused between
DragonFly and OpenBSD.
- Fix error handling for bus_dmamap_load_mbuf() so as to not try unloading
a DMA map that had not already been loaded.
- Clean up the DMA chain defragmenting path to remove unwanted printfs and
simplify things a bit.
- Have jme_encap() check the number of mapped DMA segments against the TX
ring to see if it'll fit as do most of the driver nowadays.
- Remove the KASSERT's that shouldn't be there.
- Simplify the dummy descriptor handling to be closer to the FreeBSD
driver since unlike the DragonFly driver this originated from our
driver always uses the 64-bit dummy descriptor.
- If the ring was full make sure to IF_PREPEND() the packet back on
the queue since it wasn't transmitted.
Tested by myself, comete@daknet.org and vigdis+obsd@chown.me.
|
|
|
|
kernel resumes normal (non-cold, able to run processes, etc) operation.
Previously we were relying on specific DVACT_RESUME op's in drivers
creating callback/threads themselves, but that has become too common,
indicating the need for a built-in mechanism.
ok dlg kettenis, tested by a sufficient amount of people
|
|
Don't panic in that case but force a page fault instead. Hopefully this
fixes the panic during coredump that deraadt@ reported.
|
|
|
|
|
|
Linux.
ok jsg@
|
|
|
|
driver written by Intel engineers occasionally gets them. So when we get one,
simply reset the chip, reload the firware and bring the interface up again.
Tested by naddy@, who unfortunately is experiencing the quantum zeno effect
making his iwi(4) not crap out.
ok stsp@
|
|
|
|
|
|
|
|
From Ben Mesman
117b91f41d99e88338e1f9577ced365e777a9098 in ubuntu 3.8
45a211d75137b1ac869a8a758a6667f15827a115 in mainline linux
|
|
From Chris Wilson
caf40bcc8f6751b723f0ec78e2f67beb771bfb68 in ubuntu 3.8
02978ff57a5bdfbf703d2bc5a4d933a53ede3144 in mainline linux
|
|
From Daniel Vetter
96f2e8dd3f2492d3bbf232fa0afc1e0e065e7d52 in ubuntu 3.8
ac4199e0f047546aa40172785e26c82b54bbe811 in mainline linux
|
|
From Rodrigo Vivi
349fe2edae985d44dc8ca27c6441b20408a9e184 in ubuntu 3.8
1c98b4871cca4b7ce07e19f92f934d47cf7210b0 in mainline linux
|
|
From Xiong Zhang
77e700964bdb06caf7eaf03371d7ffd4a6500199 in ubuntu 3.8
067556084a0e412013af6b0250a3143ae5afde6d in mainline linux
|
|
made it fail (WARN_ON() was evaluating its argument multiple times).
This time, also advertise support through I915_PARAM_HAS_WAIT_TIMEOUT.
|
|
Properly implement WARN_ON_ONCE() as well.
ok jsg@
|
|
|
|
|
|
driver written by Intel engineers occasionally gets them. So when we get one,
simply reset the chip, reload the firware and bring the interface up again.
tested by stsp@, pascal@
ok stsp@
|
|
|
|
after exiting X.
tested by tobiasu@
|
|
Reduces diffs with Linux.
|
|
suggested by jsg@
|
|
|