Age | Commit message (Collapse) | Author |
|
http://lists.freedesktop.org/archives/intel-gfx/2014-March/042121.html
Ben Widawsky
drm/i915/bdw: Restore PPAT on thaw
a2319c08bfd849ea32b4f890ce92df86074c5731
Ville Syrjala
drm/i915: We implement WaDisableAsyncFlipPerfMode:bdw
8285222c487b61c48b9b955b82598544c3c06050
Ben Widawsky
drm/i915/bdw: Use scratch page table for GEN8 PPGTT
8407bb9129da95fc4099b84cdbbc23e6d4f66aee
Jani Nikula
drm/i915: don't flood the logs about bdw semaphores
c923facd535b97972b5bb7d3df4fcafd61a63a5e
Ville Syrjala
drm/i915: Implement WaDisableSDEUnitClockGating:bdw
4f1ca9e94057de098d65bc7477e8f89dd51609aa
Ville Syrjala
drm/i915: Don't clobber CHICKEN_PIPESL_1 on BDW
c7c656226842679bcd9f39dc24441b4ff398a850
Kenneth Graunke
drm/i915: Add a partial instruction shootdown workaround on Broadwell.
c8966e1058e1e8ae2eec4211157847032829697a
Damien Lespiau
drm/i915/bdw: The TLB invalidation mechanism has been removed from INSTPM
dc616b89dbc4bb6a99884d214bd1ed1e0eef59a0
Kenneth Graunke
drm/i915: Add thread stall DOP clock gating workaround on Broadwell.
1411e6a57a1836ba8a3d4f17c8733b2fbaf0f005
Ville Syrjala
drm/i915: Disable semaphore wait event idle message on BDW
295e8bb73a4785b65db6655fbf6ad57c4177b551
Mika Kuoppala
drm/i915: Do forcewake reset on gen8
0a089e3355d77f758e46db54a0a81d4b58a28cc3
Mika Kuoppala
drm/i915: Fix forcewake counts for gen8
e9dbd2b20201b49b04476d2e5763faa822967913
ok kettenis@
|
|
display after waking it from standby or after VT switches. Can't seem to get
him to commit this workaround while he his hunting for a proper fix.
|
|
field from the GPT header being checksum'd. First make sure the
size is in a valid range. In particular ensure it won't cause crc32()
to run off the end of the GPT header being checksum'd. Also check
GPT signature and version first. These checks were inadvertantly
moved after the checksumming.
This should fix the system crash reported by Ze Loff on bugs@.
|
|
Local route entries, being now attached to their corresponding interface,
are susceptible to be brought DOWN when a link state change occurs. When
this happens locally configured addresses are no longer reachable.
So keep the previous (original) behavior by forcing such route entries to
always be UP.
ok sthen@, claudio@
|
|
|
|
is shared with the disk, which results in noticable latency during heavy
disk activity.
|
|
*ERROR* Hangcheck timer elapsed... xxx ring idle
messages.
|
|
also fix the confusing comment. ok guethner.
|
|
available to other areas of the kernel suffering from an overburden
of buf tweaking to read a disk sector.
ok mpi@
|
|
|
|
level 4 interrupts, just like memory controller bus errors; register the
tcc(4) handler with the right cause register bitmask, and teach imc(4) not
to claim the interrupt if it did not trigger it.
|
|
|
|
|
|
encoded with shifts. Switch to a file constructed by iterating
through i915_drv.c pciidlist so these will be included.
ok kettenis@
|
|
requested by mpi@
|
|
reclaiming to the PDU and marker input routines.
m_pullup may return a pointer to the newly allocated mbuf. In this
case m_freem is called by the trunk_input, not by the proto specific
code and pointer to the mbuf is not passed by reference. Therefore
m_freem will either be called on the middle element of the chain
(when the m_pullup call succeeds) or on the stale pointer (when it
frees the chain in the failure case). Fortunately we should never
hit this case as the receive path uniformly uses contiguous chunks
of memory.
Verified with and ok blambert, ok mpi
|
|
gpt_chk_hdr() and gpt_chk_parts().
Spotted when investigating zeloff's GPT bug report.
|
|
commit 48f8f36a6c8018c2b36ea207aaf68ef5326c5075 on the linux-3.14.y
branch of the linux-stable tree). This brings preliminary support for
the GPU on Intel's Broadwell CPUs. Don't expect these to work
perfectly yet. There are some remaining issues with older hardware as
well, but no significant regressions have been uncovered.
This also updates some of drm core code. The radeondrm code remains
based on Linux 3.8 with some minimal canges to adjust to changes in
the core drm APIs.
Joint effort with jsg@, who did the initial update of the relevant drm
core bits. Committing this early to make sure it gets more testing
and make it possible for others to help getting the remaining wrinkles
straightened out.
|
|
|
|
|
|
current ASID value rather than using zero, so that we can avoid writing
back the ASID on exit (and waste cycles because of expensive coprocessor 0
hazards).
While there, use conditional instructions when picking a random TLB set number,
in order to waste one branch prediction cache entry.
|
|
tfp_inval_icache().
|
|
Found by Matthew Dillon (Dragonfly). DMA sync hint from tedu@, ok mpi@
|
|
the firmware, rather than zeros. Matches what Linux iwlwifi does.
Spotted by Adrian Chadd (FreeBSD).
ok mpi@
|
|
|
|
|
|
This moves around calls to if_ih_insert and if_ih_remove to ensure
that we either have completed port initialization or are going to
tear the port configuration down and don't want any input processes
to get hold of the port.
When trunk_port_destroy is called from the ioctl this would wait for
all input processes to finish and release their references to be able
to disestablish the input handler and ensure full control of the port.
When switching trunkproto it is required for the ioctl context to
be able to touch all trunk ports and the protocol (tr_psc). The
easiest way do this is to disestablish all input handlers (while
making sure they all complete) and then reestablish them after the
trunk reconfiguration is completed.
This avoids getting trunk a separate locking protocol of its own.
ok mpi, suggested by and ok dlg
|
|
ok dlg, mpi
|
|
iterations and additional locking protection in the future.
Suggested by and ok mpi
|
|
and we want to limit the number of different places where we
access trunk port pointers.
trunk_watchdog should be never called as we don't set up it's
if_timer and trunk_port_watchdog just calls the if_watchdog
from the underlying interface.
It's possible that this is no longer needed due to if_slowtimo/
if_watchdog changes done earlier.
ok mpi
|
|
specific places.
ok claudio@, benno@
|
|
|
|
|
|
firmware on some machines allocates larger area whose upper part
overlaps the kernel region. Let the efiboot use lower area for its
heap. Also change its size from 3MB to 1MB and limit it by
HEAP_LIMIT.
The problem is reported by Toby Slight and Brian Conway.
|
|
data, only new
|
|
|
|
ok yasuoka@
|
|
rtrequest1(9) otherwise the route will remain attached to a stale ifa.
Found by matthieu@
|
|
in in_pcbbind() and in6_pcbsetport()
ok claudio@, with input from David Hill
|
|
|
|
it could be supported by rtwn(4) eventualy
ok stsp@
|
|
remove one from constructs based upon it) when building for R8000.
|
|
consistency with PQ_AOBJ.
Input kettenis@, ok beck@
|
|
From David Hill, ok sthen@
|
|
Found by benno@.
ok phessler@, claudio@, benno@
|
|
Same diff as guenther@ committed for alpha.
ok guenther@
|
|
Same diff as guenther@ committed for alpha.
ok guenther@
|
|
Problem noticed and initial diff by kettenis@
ok kettenis@ visa@ dlg@
|
|
ok miod
|
|
|