GitHub PushEvent at 2014-06-14 05:32:05
Repository: HybridMix
Actor: pattyboi
Payload: {"shas":[["84dd6fc7f3139aefe3ec6c306e5b3d5156559577","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","reclaim some ram","pattyboi",true],["1755663df2232f48b2ccb25813b4a6a05ca47932","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","lmk from ak","pattyboi",true],["c5f6dc2bb40f6d9150b6a978154cb9e87583bfc6","f8ab2c5e1dd93cba379c44b5945c0110170970c1@codeaurora.org","ksm: Provide support to use deferred timers for scanner thread\n\nKSM thread to scan pages is getting schedule on definite timeout.\nThat wakes up CPU from idle state and hence may affect the power\nconsumption. Provide an optional support to use deferred timer\nwhich suites low-power use-cases.\n\nTo enable deferred timers,\n$ echo 1 > /sys/kernel/mm/ksm/deferred_timer\n\nChange-Id: I07fe199f97fe1f72f9a9e1b0b757a3ac533719e8\nSigned-off-by: Chintan Pandya <cpandya@codeaurora.org>","Chintan Pandya",true],["523851c47031c05bb1d3b33808f7503027b25b99","733e8b735f714777b0faecdbf6b8d6fe0eff8dac@freenet.de","Backport some pm functions to be ready for: Two flags for\n async suspend_noirq and suspend_late Asynchronous threads for resume_noirq\n ...","Quallenauge",true],["4455e9b6472d07a1f9fae9c490bc7a465a69b739","733e8b735f714777b0faecdbf6b8d6fe0eff8dac@freenet.de","PM-sleep-Asynchronous-threads-for-resume_noirq","Quallenauge",true],["2d97795869d46a6ae2a0256a84bba1b9d1dca9cd","733e8b735f714777b0faecdbf6b8d6fe0eff8dac@freenet.de","PM-sleep-Asynchronous-threads-for-resume_noirq","Quallenauge",true],["7e7f5830efd5028ae7616bb40a8ee6c5ddb18723","733e8b735f714777b0faecdbf6b8d6fe0eff8dac@freenet.de","Add missing mutex_unlock() call to prevent deadlocks.","Quallenauge",true],["42af095f0a3cacf4f3e08ead6b56e2fa96717d5b","d6930da0d649c01d063dcca4d796c2ac2cbb68ba@ti.com","dma-buf: Introduce dma buffer sharing mechanism\n\n dma-buf: Introduce dma buffer sharing mechanism\n\nThis is the first step in defining a dma buffer sharing mechanism.\n\nA new buffer object dma_buf is added, with operations and API to allow easy\nsharing of this buffer object across devices.\n\nThe framework allows:\n- creation of a buffer object, its association with a file pointer, and\n   associated allocator-defined operations on that buffer. This operation is\n   called the 'export' operation.\n- different devices to 'attach' themselves to this exported buffer object, to\n  facilitate backing storage negotiation, using dma_buf_attach() API.\n- the exported buffer object to be shared with the other entity by asking for\n   its 'file-descriptor (fd)', and sharing the fd across.\n- a received fd to get the buffer object back, where it can be accessed using\n   the associated exporter-defined operations.\n- the exporter and user to share the scatterlist associated with this buffer\n   object using map_dma_buf and unmap_dma_buf operations.\n\nAtleast one 'attach()' call is required to be made prior to calling the\nmap_dma_buf() operation.\n\nCouple of building blocks in map_dma_buf() are added to ease introduction\nof sync'ing across exporter and users, and late allocation by the exporter.\n\nFor this first version, this framework will work with certain conditions:\n- *ONLY* exporter will be allowed to mmap to userspace (outside of this\n   framework - mmap is not a buffer object operation),\n- currently, *ONLY* users that do not need CPU access to the buffer are\n   allowed.\n\nMore details are there in the documentation patch.\n\nThis is based on design suggestions from many people at the mini-summits[1],\nmost notably from Arnd Bergmann <arnd@arndb.de>, Rob Clark <rob@ti.com> and\nDaniel Vetter <daniel@ffwll.ch>.\n\nThe implementation is inspired from proof-of-concept patch-set from\nTomasz Stanislawski <t.stanislaws@samsung.com>, who demonstrated buffer sharing\nbetween two v4l2 devices. [2]\n\n[1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement\n[2]: http://lwn.net/Articles/454389\n\nSigned-off-by: Sumit Semwal <sumit.semwal@linaro.org>\nSigned-off-by: Sumit Semwal <sumit.semwal@ti.com>\nReviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nReviewed-by: Dave Airlie <airlied@redhat.com>\nReviewed-and-Tested-by: Rob Clark <rob.clark@linaro.org>\nSigned-off-by: Dave Airlie <airlied@redhat.com>\n\nConflicts:\ndrivers/base/Makefile","Sumit Semwal",true],["ce23b9cdce4750eba7d06963516640125f32939c","3ded2f39a78f0d7044839546f95841842b4d7c96@ideasonboard.com","dma-buf: Constify ops argument to dma_buf_export()\n\nThis allows drivers to make the dma buf operations structure constant.\n\nSigned-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nReviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Sumit Semwal <sumit.semwal@linaro.org>","Laurent Pinchart",true],["6dee2c1c6a2b630c3f279e3afb7b170b3270e2f5","3ded2f39a78f0d7044839546f95841842b4d7c96@ideasonboard.com","dma-buf: Remove unneeded sanity checks\n\nops, ops->map_dma_buf and ops->unmap_dma_buf are guaranteed to be\nnon-NULL by a check in dma_buf_export(). Remove NULL checks on those\nvariables in the other API functions.\n\nSigned-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nReviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Sumit Semwal <sumit.semwal@linaro.org>","Laurent Pinchart",true],["b49549ad7feea988f76c4feb857d6092fb5f900c","3ded2f39a78f0d7044839546f95841842b4d7c96@ideasonboard.com","dma-buf: Return error instead of using a goto statement when possible\n\nRemove an error label in dma_buf_attach() that just returns an error\ncode.\n\nSigned-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nReviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Sumit Semwal <sumit.semwal@linaro.org>","Laurent Pinchart",true],["bc346c9a696cd4f9f359b7cb19eec2f621120aa9","3ded2f39a78f0d7044839546f95841842b4d7c96@ideasonboard.com","dma-buf: Move code out of mutex-protected section in dma_buf_attach()\n\nSome fields can be set without mutex protection. Initialize them before\nlocking the mutex.\n\nSigned-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nReviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Sumit Semwal <sumit.semwal@linaro.org>","Laurent Pinchart",true],["a6fedd694a12ce9536d8c436c986450de0151102","d6930da0d649c01d063dcca4d796c2ac2cbb68ba@ti.com","dma-buf: add dma_data_direction to unmap dma_buf_op\n\nSome exporters may use DMA map/unmap APIs in dma-buf ops, which require\nenum dma_data_direction for both map and unmap operations.\n\nThus, the unmap dma_buf_op also needs to have enum dma_data_direction as\na parameter.\n\nReported-by: Tomasz Stanislawski <t.stanislaws@samsung.com>\nSigned-off-by: Sumit Semwal <sumit.semwal@ti.com>\nReviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Sumit Semwal <sumit.semwal@linaro.org>","Sumit Semwal",true],["be32add73e1d4fef289478a17ca77463edc599ef","f2295d84e358395675bc8031be58672073ae065e@redhat.com","dma-buf: pass flags into dma_buf_fd.\n\nWe need to pass the flags into dma_buf_fd at this point,\nso the flags end up doing the right thing for O_CLOEXEC.\n\nSigned-off-by: Dave Airlie <airlied@redhat.com>\nSigned-off-by: Rob Clark <rob@ti.com>\nSigned-off-by: Sumit Semwal <sumit.semwal@linaro.org>","Dave Airlie",true],["60dafffff9ec0d83e3b3cad0a4a553afa90b43c7","c1b6782c4af8f0673da8923a0702a1832e5940f4@ffwll.ch","dma-buf: don't hold the mutex around map/unmap calls\n\nThe mutex protects the attachment list and hence needs to be held\naround the callbakc to the exporters (optional) attach/detach\nfunctions.\n\nHolding the mutex around the map/unmap calls doesn't protect any\ndma_buf state. Exporters need to properly protect any of their own\nstate anyway (to protect against calls from their own interfaces).\nSo this only makes the locking messier (and lockdep easier to anger).\n\nTherefore let's just drop this.\n\nv2: Rebased on top of latest dma-buf-next git.\n\nSigned-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nReviewed-by: Rob Clark <rob.clark@linaro.org>\nSigned-off-by: Sumit Semwal <sumit.semwal@linaro.org>","Daniel Vetter",true],["9de74f9b7afab6795f3f85230baf5a2d6ee24fb0","c1b6782c4af8f0673da8923a0702a1832e5940f4@ffwll.ch","dma-buf: add support for kernel cpu access\n\nBig differences to other contenders in the field (like ion) is\nthat this also supports highmem, so we have to split up the cpu\naccess from the kernel side into a prepare and a kmap step.\n\nPrepare is allowed to fail and should do everything required so that\nthe kmap calls can succeed (like swapin/backing storage allocation,\nflushing, ...).\n\nMore in-depth explanations will follow in the follow-up documentation\npatch.\n\nChanges in v2:\n\n- Clear up begin_cpu_access confusion noticed by Sumit Semwal.\n- Don't automatically fallback from the _atomic variants to the\n  non-atomic variants. The _atomic callbacks are not allowed to\n  sleep, so we want exporters to make this decision explicit. The\n  function signatures are explicit, so simpler exporters can still\n  use the same function for both.\n- Make the unmap functions optional. Simpler exporters with permanent\n  mappings don't need to do anything at unmap time.\n\nChanges in v3:\n\n- Adjust the WARN_ON checks for the new ->ops functions as suggested\n  by Rob Clark and Sumit Semwal.\n- Rebased on top of latest dma-buf-next git.\n\nChanges in v4:\n\n- Fixup a missing - in a return -EINVAL; statement.\n\nSigned-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Rob Clark <rob@ti.com>\nSigned-off-by: Sumit Semwal <sumit.semwal@linaro.org>","Daniel Vetter",true],["4f037281850bb0c4dcc2c6d618502fe3cf3ef6ce","c1b6782c4af8f0673da8923a0702a1832e5940f4@ffwll.ch","dma-buf: mmap support\n\nCompared to Rob Clark's RFC I've ditched the prepare/finish hooks\nand corresponding ioctls on the dma_buf file. The major reason for\nthat is that many people seem to be under the impression that this is\nalso for synchronization with outstanding asynchronous processsing.\nI'm pretty massively opposed to this because:\n\n- It boils down reinventing a new rather general-purpose userspace\n  synchronization interface. If we look at things like futexes, this\n  is hard to get right.\n- Furthermore a lot of kernel code has to interact with this\n  synchronization primitive. This smells a look like the dri1 hw_lock,\n  a horror show I prefer not to reinvent.\n- Even more fun is that multiple different subsystems would interact\n  here, so we have plenty of opportunities to create funny deadlock\n  scenarios.\n\nI think synchronization is a wholesale different problem from data\nsharing and should be tackled as an orthogonal problem.\n\nNow we could demand that prepare/finish may only ensure cache\ncoherency (as Rob intended), but that runs up into the next problem:\nWe not only need mmap support to facilitate sw-only processing nodes\nin a pipeline (without jumping through hoops by importing the dma_buf\ninto some sw-access only importer), which allows for a nicer\nION->dma-buf upgrade path for existing Android userspace. We also need\nmmap support for existing importing subsystems to support existing\nuserspace libraries. And a loot of these subsystems are expected to\nexport coherent userspace mappings.\n\nSo prepare/finish can only ever be optional and the exporter /needs/\nto support coherent mappings. Given that mmap access is always\nsomewhat fallback-y in nature I've decided to drop this optimization,\ninstead of just making it optional. If we demonstrate a clear need for\nthis, supported by benchmark results, we can always add it in again\nlater as an optional extension.\n\nOther differences compared to Rob's RFC is the above mentioned support\nfor mapping a dma-buf through facilities provided by the importer.\nWhich results in mmap support no longer being optional.\n\nNote that this dma-buf mmap patch does _not_ support every possible\ninsanity an existing subsystem could pull of with mmap: Because it\ndoes not allow to intercept pagefaults and shoot down ptes importing\nsubsystems can't add some magic of their own at these points (e.g. to\nautomatically synchronize with outstanding rendering or set up some\nspecial resources). I've done a cursory read through a few mmap\nimplementions of various subsytems and I'm hopeful that we can avoid\nthis (and the complexity it'd bring with it).\n\nAdditonally I've extended the documentation a bit to explain the hows\nand whys of this mmap extension.\n\nIn case we ever want to add support for explicitly cache maneged\nuserspace mmap with a prepare/finish ioctl pair, we could specify that\nuserspace needs to mmap a different part of the dma_buf, e.g. the\nrange starting at dma_buf->size up to dma_buf->size*2. This works\nbecause the size of a dma_buf is invariant over it's lifetime. The\nexporter would obviously need to fall back to coherent mappings for\nboth ranges if a legacy clients maps the coherent range and the\narchitecture cannot suppor conflicting caching policies. Also, this\nwould obviously be optional and userspace needs to be able to fall\nback to coherent mappings.\n\nv2:\n- Spelling fixes from Rob Clark.\n- Compile fix for !DMA_BUF from Rob Clark.\n- Extend commit message to explain how explicitly cache managed mmap\n  support could be added later.\n- Extend the documentation with implementations notes for exporters\n  that need to manually fake coherency.\n\nChange-Id: Ia8f2ae5d8a1b1c87ed12ca1c89d7bf2067239ee4\nCc: Rob Clark <rob.clark@linaro.org>\nCc: Rebecca Schultz Zavin <rebecca@android.com>\nSigned-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>","Daniel Vetter",true],["9a9d1ac1cfe173a6e1372e0c83729b3ab13729e2","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","enable dma shared buffers","pattyboi",true],["cff99e7c8d70abd61095f19d118d88770241246f","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","enable fast chage by default","pattyboi",true],["bdce51d87ca95cff2abb1064ffde241dfed36067","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","config stuff","pattyboi",true]],"size":22,"ref":"refs/heads/Real","head":"9e35dd682e28fb53cff1546e7288ccf8f0a874e3"}