{"push_id":873166443,"size":9,"distinct_size":0,"ref":"refs/heads/staging/fixes","head":"95b15d9ff7dc123ab5afc486f72f891e3d3aac92","before":"35f3748dcd99e5a3c96efa82ca46fbe260e98e68","commits":[{"sha":"68a846b84f0a0a22579c5f89b581708bdfd83096","author":{"email":"d9f27fb07c1e9f131223ad827fa5179f3846c30b@redhat.com","name":"Ben Skeggs"},"message":"WIPce/gk104: attempt at better handling of LAUNCHERR\n\nVery rough, no idea how correct it is at this point, but it prevents\ngetteximage-depth from piglit from hanging the GPU.\n\nv2: updated with NV_PCE_FE_LAUNCHERR_REPORT values provided by NVIDIA\n\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/Gnurou/nouveau/commits/68a846b84f0a0a22579c5f89b581708bdfd83096"},{"sha":"8614a4bd46d723a0d5b490a2f25b05e28d2caa83","author":{"email":"5ea228a5cf8d16f5020fb76be180e36823a0ff47@nvidia.com","name":"Vince Hsu"},"message":"fifo/gk104: fix engine status register offset\n\nThe offset should be 8 on Kepler and later.\n\nSigned-off-by: Vince Hsu <vinceh@nvidia.com>\nReviewed-by: Alexandre Courbot <acourbot@nvidia.com>\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/Gnurou/nouveau/commits/8614a4bd46d723a0d5b490a2f25b05e28d2caa83"},{"sha":"e13eb9bff980c319741b01e9cef89907b0d04f6b","author":{"email":"4ea09192621d02805f41333c23b79bb050a76588@gmail.com","name":"Nicolas Chauvet"},"message":"gk20a: Add MODULE_FIRMWARE for gk20a\n\nThis patch is needed by initramfs tools to detect\nthe required firmware files for the module.\n\nThis patch tests for either TEGRA_124_SOC or TEGRA_132_SOC\nfor the firmwares related to the Tegra K1 generation.\n\nv2: move the MODULE_FIRMWARE to the nvidia_platform.c file.\n This will avoid to test for NOUVEAU_PLATFORM_DRIVER\n\nSigned-off-by: Nicolas Chauvet <kwizart@gmail.com>\nReviewed-by: Alexandre Courbot <acourbot@nvidia.com>\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/Gnurou/nouveau/commits/e13eb9bff980c319741b01e9cef89907b0d04f6b"},{"sha":"2887ad9613aecada1ebd3867da7bc1cfe605f691","author":{"email":"301cd6a3ea50a894b4b51e385c5eb12b9a4ffc0c@nvidia.com","name":"Alexandre Courbot"},"message":"instmem/gk20a: fix race conditions\n\nThe LRU list used for recycling CPU mappings was handling concurrency\nvery poorly. For instance, if an instobj was acquired twice before being\nreleased once, it would end up into the LRU list even though there is\nstill a client accessing it.\n\nThis patch fixes this by properly counting how many clients are\ncurrently using a given instobj.\n\nWhile at it, we also raise errors when inconsistencies are detected, and\nfactorize some code.\n\nSigned-off-by: Alexandre Courbot <acourbot@nvidia.com>\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/Gnurou/nouveau/commits/2887ad9613aecada1ebd3867da7bc1cfe605f691"},{"sha":"0bcbe9b455c0f419454815a76eba463403b9c3be","author":{"email":"301cd6a3ea50a894b4b51e385c5eb12b9a4ffc0c@nvidia.com","name":"Alexandre Courbot"},"message":"instmem/gk20a: use DMA API CPU mapping\n\nCommit 69c4938249fb (\"drm/nouveau/instmem/gk20a: use direct CPU access\")\ntried to be smart while using the DMA-API by managing the CPU mappings of\nbuffers allocated with the DMA-API by itself. In doing so, it relied\non dma_to_phys() which is an architecture-private function not\navailable everywhere. This broke the build on several architectures.\n\nSince there is no reliable and portable way to obtain the physical\naddress of a DMA-API buffer, stop trying to be smart and just use the\nCPU mapping that the DMA-API can provide. This means that buffers will\nbe CPU-mapped for all their life as opposed to when we need them, but\nanyway using the DMA-API here is a fallback for when no IOMMU is\navailable so we should not expect optimal behavior.\n\nThis makes the IOMMU and DMA-API implementations of instmem diverge\nenough that we should maybe put them into separate files...\n\nSigned-off-by: Alexandre Courbot <acourbot@nvidia.com>\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/Gnurou/nouveau/commits/0bcbe9b455c0f419454815a76eba463403b9c3be"},{"sha":"fcd74e81e65aee8a2a33bdca3142a5358dac7582","author":{"email":"d9f27fb07c1e9f131223ad827fa5179f3846c30b@redhat.com","name":"Ben Skeggs"},"message":"bios: return actual size of the buffer retrieved via _ROM\n\nFixes detection of a failed attempt at fetching the entire ROM image\nin one-shot (a violation of the spec, that works a lot of the time).\n\nTested on a HP Zbook 15 G2.\n\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>","distinct":false,"url":"https://api.github.com/repos/Gnurou/nouveau/commits/fcd74e81e65aee8a2a33bdca3142a5358dac7582"},{"sha":"57a4bbb7c269b8f88770c498048bbd044745013c","author":{"email":"301cd6a3ea50a894b4b51e385c5eb12b9a4ffc0c@nvidia.com","name":"Alexandre Courbot"},"message":"tegra: compile fixes","distinct":false,"url":"https://api.github.com/repos/Gnurou/nouveau/commits/57a4bbb7c269b8f88770c498048bbd044745013c"},{"sha":"4bf0f3b5058698563a6f32371ac859582f28b3c8","author":{"email":"301cd6a3ea50a894b4b51e385c5eb12b9a4ffc0c@nvidia.com","name":"Alexandre Courbot"},"message":"fifo/gm20b: kick channel during cleanup\n\nGM20B requires a channel kick to be performed during gpfifo cleanup, or\nthe FIFO will attempt to fetch memory from the previous context as a\nchannel is recycled. A previous commit attempted to do this for all\nKepler GPUs, but due to bug reports that pinned it down it has been\nreverted. The present commit limits its scope to GM20B only.\n\nThe only effective change of this patch is to add a call to\ngk104_fifo_gpfifo_kick() in gpfifo_fini for GM20B, but doing so requires\nto export quite a few extra functions, hence its non-trivial length.\n\nSigned-off-by: Alexandre Courbot <acourbot@nvidia.com>","distinct":false,"url":"https://api.github.com/repos/Gnurou/nouveau/commits/4bf0f3b5058698563a6f32371ac859582f28b3c8"},{"sha":"95b15d9ff7dc123ab5afc486f72f891e3d3aac92","author":{"email":"301cd6a3ea50a894b4b51e385c5eb12b9a4ffc0c@nvidia.com","name":"Alexandre Courbot"},"message":"instmem/gk20a: add write barrier when releasing DMA object\n\nWhen using the DMA-API for instmem, we may obtain a write-combined\nmapping. For such cases, add a write barrier in\ngk20a_instobj_release_dma() to make sure that all writes have reached\nmemory at this time.\n\nSigned-off-by: Alexandre Courbot <acourbot@nvidia.com>","distinct":false,"url":"https://api.github.com/repos/Gnurou/nouveau/commits/95b15d9ff7dc123ab5afc486f72f891e3d3aac92"}]}