{"push_id":985833020,"size":70,"distinct_size":70,"ref":"refs/heads/saberTest-permissive","head":"290de27c1a87eea6562a402ab0b400867ad31397","before":"a0e577bc96650e9a5903aa6e16349c60971c3536","commits":[{"sha":"3191974b852f2e34b0c7049065181b2bfac00f7f","author":{"email":"d688953a19dcb476c5fb90e6abba87f77b09be65@gmail.com","name":"Pranav Vashi"},"message":"Revert \"exec: reserve full virtual stack space at execve()\"\n\n* As reported by @Dorimanx, this commit captured large amount of RAM\n  and can trigger OOM. Revert. Thanks Yuri.\n\nThis reverts commit ec2adc5273429d52700ac9e497d03bbcfd498c4a.","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/3191974b852f2e34b0c7049065181b2bfac00f7f"},{"sha":"5da1d7f8739925714953ae0183acce969d2caa54","author":{"email":"f6edf8d75b12405268138518fb6571756adf9446@codeaurora.org","name":"Ben Romberger"},"message":"ASoC: msm: qdsp6v2: Correctly free ASM no wait queue\n\nRemove improper deletion of list head and protect list\ndeletion with spinlock. Spinlock protects the list\nfrom access in ADSP callback at the same time the\nlist is being deallocated.\n\nChange-Id: I1b102cd99e7c80e1dfd4e2054b9ba7e0ca26d6a7\nSigned-off-by: Ben Romberger <bromberg@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/5da1d7f8739925714953ae0183acce969d2caa54"},{"sha":"3090702a0f671f1849ed7b945a3311abb5269e43","author":{"email":"8d48a408e9de05c3de2551b9a896accea88a2f97@motorola.com","name":"Joel Voss"},"message":"IKSWL-3373: selinux: Improve avc logging\n\nWhere applicable, include the process UID in the audit\nlog message. This assists debugging the source of denials,\nespecially in the application domain.\n\nChange-Id: I082398f0216db893b51f9371f98e6b230d2e9147\nSigned-off-by: Joel Voss <jvoss@motorola.com>\nReviewed-by: Connie Zhao <czhao1@motorola.com>\nReviewed-on: http://gerrit.mot.com/689473\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Christopher Fries <cfries@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>\nSigned-off-by: kgudeth <kgudeth@motorola.com>\nReviewed-on: http://gerrit.mot.com/695886\nReviewed-on: http://gerrit.mot.com/727995\nSME-Granted: SME Approvals Granted\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/3090702a0f671f1849ed7b945a3311abb5269e43"},{"sha":"47deaa0b90ca0983aa76da35c8ee4365fe28d597","author":{"email":"872f71ea18f72c0748629a56d0a990d2fe86539f@gmail.com","name":"f100cleveland"},"message":"ASoC: wcd9330: Correct HPH turn on and shutdown sequences\n\n  There is glitch on BUCK_OUT and NCP_VNEG when doing HPH shutdown\nsequences. The root cause is NCP is not turned off before Class H\nblock disabled.\n  For HPH turnon sequences, make sure NCP turn on happens after Class\nH block enabled.\n  For HPH shutdown sequences, make sure NCP turn off happens before\nClass H block disabled. Ensure the clock is disabled after turning\noff the class-H controller\n\nCRs-Fixed: 890588\nChange-Id: I880806c0a7284aa22c9d78286efbed73544b2356\nSigned-off-by: Walter Yang <yandongy@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/47deaa0b90ca0983aa76da35c8ee4365fe28d597"},{"sha":"98d8021f063acb3afba2b95094619b63a377faf5","author":{"email":"872f71ea18f72c0748629a56d0a990d2fe86539f@gmail.com","name":"f100cleveland"},"message":"ASoC: wcd9330: Disable compander in HPH when EAR is enabled\n\nRX1 is shared between EAR and HPH; when HPH is enabled,\ncompander is also enabled which causes noise in EAR.\nThis change disables compander when EAR path is enabled\nand avoids enabling compander if EAR is already enabled.\n\nChange-Id: Ic57dbc9e74bbed4a32f024b83dd333beb84b7c5f\nSigned-off-by: Roberto Granados Dorado <robertog@codeaurora.org>\nSigned-off-by: Phani Kumar Uppalapati <phaniu@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/98d8021f063acb3afba2b95094619b63a377faf5"},{"sha":"a9caeccc9e89963947960f85c6ed2e916a277265","author":{"email":"872f71ea18f72c0748629a56d0a990d2fe86539f@gmail.com","name":"f100cleveland"},"message":"ASoC: qdsp6v2: Squashed upstream audio offload improvements\n\nSoC: msm: qdsp6v2: Enable gapless for pcm offload\n\nEnable gapless for PCM offload format playback.\n\nSigned-off-by: Chaithanya Krishna Bacharaju <chaithan@codeaurora.org>\n\nASoC: msm: qdsp6v2: fix incomplete playback issue for non-gapless formats\n\nFix data loss on auto switching of playback to next clip\nwhen current playback format is not having gapless support\nin compressed driver.\nMedia playback complete event is sent to framework on completion\nof partial drain, this is supposed to be before actual renderer\nEOS by duration equal to value of PARTIAL_DRAIN_ACK_EARLY_BY_MSEC,\nbut due to uninitialized frame size for non-gapless formats this\nduration calculated is inaccurate and sometimes triggers drain\ncompletion too early, leading to premature teardown of playback\nsession.\nFix this by disabling gapless on formats not having valid gapless\nparameters.\nRecalculate partial drain delay based on flac min block size\nto avoid incorrect drain delay for FLAC format.\n\nSigned-off-by: Dhananjay Kumar <dhakumar@codeaurora.org>\n\nASoC: msm: qdsp6v2: move frame info to be per session based\n\nWhen audio stream manager returns READ_DONE event, the payload\nwhich comes with the event contains size of captured audio data\nand offset indicating where the data starts in the buffer.\nBefore this change, size and offset information is stored in\nglobal variable which can be shared by all capture sessions.\nIf the offset is overwritten by another session with larger value,\nbuffer can be indexed beyond actual size of buffer when copying\ncaptured data into user-space buffer. Move the structure as part\nof per session private data to prevent overwriting.\n\nSigned-off-by: Patrick Lai <plai@codeaurora.org>\nSigned-off-by: Banajit Goswami <bgoswami@codeaurora.org>\n\nASoC: msm: qdsp6v2: make frame info to static array\n\nFrame info which track size of captured data and offset is dyanmically\nallocated data. Some crashes are reported due to frame info is used after\nfree. Error type is null pointer dereference. Total size of frame info is\nrelatively small and it is part of msm_audio which is dynamically\nallocated structure. No need to allocate and track it separately.\n\nSigned-off-by: Fred Oh <fred@codeaurora.org>\n\nASoC: msm: qdsp6v2: Track no wait commands\n\nAdd a command queue for no wait commands. Use queue\nto track all active no wait commands and remove\nthem from the queue when they have correctly\nreturned. If a queue is not used, a wait command\ncould be improperly recognized as a no wait\ncommand and cause a timeout.\n\nSigned-off-by: Ben Romberger <bromberg@codeaurora.org>\n\nASoC: msm: qdsp6v2: Check memory before re-mapping cal block\n\nCheck that the memory was correctly allocated\nfor the calibration block before re-mapping\nthe calibration block to the ADSP.\n\nSigned-off-by: Ben Romberger <bromberg@codeaurora.org>\n\nASoC: msm: qdsp6v2: Initialize ASM no wait spinlock\n\nInitialize spinlock for the no wait queue. The\nspin_lock_init function is now called for the\nspinlock on init for the audio client structure.\n\nSigned-off-by: Ben Romberger <bromberg@codeaurora.org>\n\nASoC: msm: Interrupt events in compress free\n\nInterrupt any wait events during free of the compress driver\nand move spinlock unlock to after the ASM client is freed.\n\nSigned-off-by: Ben Romberger <bromberg@codeaurora.org>\n\nASoC: msm: qdsp6v2: Prevent ASM callback when client freed\n\nSet EOS flag in compress driver for partial drain\nand reorder ASM client free function to prevent\ncallback from being signaled after ASM client is\nfreed.\n\nSigned-off-by: Ben Romberger <bromberg@codeaurora.org>\n\nASoC: msm: qdsp6v2: Move asm list init before apr registration\n\nMove list init for no wait que before apr registration.\nIf apr registration fails asm free client will free\nthe no wait que.\n\nSigned-off-by: Ben Romberger <bromberg@codeaurora.org>\n\nASoC: msm: qdsp6v2: add error handling on write done during partial drain\n\n If there is any error on write done event during parital drain,\n compress driver does not return from partial drain and playback\n does not move to next clip.\n Add error handling in compress driver to return from partial\n drain on write done error.\n\nSigned-off-by: Preetam Singh Ranawat <apranawat@codeaurora.org>\n\nASoC: msm: qdsp6v2: add more supported sampling rates\n\nSome of sampling rates are missed. More sampling rates are supported.\n\nSigned-off-by: Fred Oh <fred@codeaurora.org>\n\nASoC: msm: fix indefinite wait in compress drain\n\nIn compressed driver streams might get stopped while\nioctl drain is started but not completed, since buffers\nare drained in multiple stages when gapless mode is\nenabled.\nCheck stream state before issuing wait commands to\nprevent waiting for drain ack on stopped streams.\n\nSigned-off-by: Dhananjay Kumar <dhakumar@codeaurora.org>\n\nALSA: compress: fix an integer overflow check\n\nI previously added an integer overflow check here but looking at it now,\nit's still buggy.\n\nThe bug happens in snd_compr_allocate_buffer().  We multiply\n\".fragments\" and \".fragment_size\" and that doesn't overflow but then we\nsave it in an unsigned int so it truncates the high bits away and we\nallocate a smaller than expected size.\n\nChange-Id: I3910bcdc732763d9208e765d6ca69853a0cddeda\nFixes: b35cc8225845 ('ALSA: compress_core: integer overflow in snd_compr_allocate_buffer()')\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/a9caeccc9e89963947960f85c6ed2e916a277265"},{"sha":"91d506b8a699f3cbd5f3398e8cbb88f0255f8702","author":{"email":"872f71ea18f72c0748629a56d0a990d2fe86539f@gmail.com","name":"f100cleveland"},"message":"usb: gadget: mass_storage: added sysfs entry for cdrom to LUNs\n\nThis patch adds a \"cdrom\" sysfs entry for each mass_storage LUN, just\nlike \"ro\" sysfs entry. This allows switching between USB and CD-ROM\nemulation without reinserting the module or recompiling the kernel.\n\nChange-Id: Idf83c74815b1ad370428ab9d3e5503d5f7bcd3b6\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/91d506b8a699f3cbd5f3398e8cbb88f0255f8702"},{"sha":"16db89eafa663ba841d0c60511e8722ccd3ae9fe","author":{"email":"9bbe2bc2582c2f5524e29c40bc5f39feafbfd193@lge.com","name":"Bongkyu Kim"},"message":"UPSTREAM: lz4: fix wrong compress buffer size for 64-bits\n\n(cherry picked from commit 06af1c52c9ea234e0b1266cc0b52c3e0c6c8fe9f)\n\nThe current lz4 compress buffer is 16kb on 32-bits, 32kb on 64-bits\nsystem.  But, lz4 needs only 16kb on both.  On 64-bits, this causes\nwasted cpu cycles for additional memset during every compression.\n\nIn case of lz4hc, the current buffer size is (256kb + 8) on 32-bits,\n(512kb + 16) on 64-bits.  But, lz4hc needs only (256kb + 2 * pointer) on\nboth.\n\nThis patch fixes these wrong compress buffer sizes for 64-bits.\n\nSigned-off-by: Bongkyu Kim <bongkyu.kim@lge.com>\nCc: Chanho Min <chanho.min@lge.com>\nCc: Yann Collet <yann.collet.73@gmail.com>\nCc: Kyungsik Lee <kyungsik.lee@lge.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/16db89eafa663ba841d0c60511e8722ccd3ae9fe"},{"sha":"da804e4ec0374be4ad8723d89faa384edc1c5770","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4 crypto: fix memory leak in ext4_bio_write_page()\n\nThere are times when ext4_bio_write_page() is called even though we\ndon't actually need to do any I/O.  This happens when ext4_writepage()\ngets called by the jbd2 commit path when an inode needs to force its\npages written out in order to provide data=ordered guarantees --- and\na page is backed by an unwritten (e.g., uninitialized) block on disk,\nor if delayed allocation means the page's backing store hasn't been\nallocated yet.  In that case, we need to skip the call to\next4_encrypt_page(), since in addition to wasting CPU, it leads to a\nbounce page and an ext4 crypto context getting leaked.\n\nChange-Id: I6edf928aea9a49df1a903091271935492bc63b7a\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: \"Theodore Ts'o\" <tytso@google.com>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/da804e4ec0374be4ad8723d89faa384edc1c5770"},{"sha":"a7a0ee412892eadb50a2ff21ddae5f38af39774e","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4 crypto: ext4_page_crypto() doesn't need a encryption context\n\nSince ext4_page_crypto() doesn't need an encryption context (at least\nnot any more), this allows us to simplify a number function signature\nand also allows us to avoid needing to allocate a context in\next4_block_write_begin().  It also means we no longer need a separate\next4_decrypt_one() function.\n\nChange-Id: Icb9beb8f54136f7628828a201de92b4a6f34317b\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: \"Theodore Ts'o\" <tytso@google.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/a7a0ee412892eadb50a2ff21ddae5f38af39774e"},{"sha":"4d03ee84ae342b289cd9d09cb8611eeb251cd9a0","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4 crypto: replace some BUG_ON()'s with error checks\n\nBuggy (or hostile) userspace should not be able to cause the kernel to\ncrash.\n\nChange-Id: I6ae00d9d4934c254ed8423996646b342fefeb740\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: \"Theodore Ts'o\" <tytso@google.com>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/4d03ee84ae342b289cd9d09cb8611eeb251cd9a0"},{"sha":"520005422b49a284c27131fe058bc8e927b37abc","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4 crypto: fix bugs in ext4_encrypted_zeroout()\n\nFix multiple bugs in ext4_encrypted_zeroout(), including one that\ncould cause us to write an encrypted zero page to the wrong location\non disk, potentially causing data and file system corruption.\nFortunately, this tends to only show up in stress tests, but even with\nthese fixes, we are seeing some test failures with generic/127 --- but\nthese are now caused by data failures instead of metadata corruption.\n\nSince ext4_encrypted_zeroout() is only used for some optimizations to\nkeep the extent tree from being too fragmented, and\next4_encrypted_zeroout() itself isn't all that optimized from a time\nor IOPS perspective, disable the extent tree optimization for\nencrypted inodes for now.  This prevents the data corruption issues\nreported by generic/127 until we can figure out what's going wrong.\n\nChange-Id: I18c829d20994c6567db64e3f2e5cee0632ac8b18\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: \"Theodore Ts'o\" <tytso@google.com>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/520005422b49a284c27131fe058bc8e927b37abc"},{"sha":"8eb47ab0608e294e5397bbd08886d83463765270","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4 crypto: use a jbd2 transaction when adding a crypto policy\n\nStart a jbd2 transaction, and mark the inode dirty on the inode under\nthat transaction after setting the encrypt flag.  Otherwise if the\ndirectory isn't modified after setting the crypto policy, the\nencrypted flag might not survive the inode getting pushed out from\nmemory, or the the file system getting unmounted and remounted.\n\nChange-Id: Ie92e8317cd5faa7c7681ff54b90356275c307844\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Theodore Ts'o <tytso@google.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/8eb47ab0608e294e5397bbd08886d83463765270"},{"sha":"36fd2ab3ba05347d4faf8d36ecd345c238027a9a","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4 crypto: check for too-short encrypted file names\n\nAn encrypted file name should never be shorter than an 16 bytes, the\nAES block size.  The 3.10 crypto layer will oops and crash the kernel\nif ciphertext shorter than the block size is passed to it.\n\nFortunately, in modern kernels the crypto layer will not crash the\nkernel in this scenario, but nevertheless, it represents a corrupted\ndirectory, and we should detect it and mark the file system as\ncorrupted so that e2fsck can fix this.\n\nChange-Id: I886fc9cdd6512fb7436709d5a6a6dbd05c21da5a\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Theodore Ts'o <tytso@google.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/36fd2ab3ba05347d4faf8d36ecd345c238027a9a"},{"sha":"e79f8e6d4beea7ef6fa2ed52a96e6e3f4274bc94","author":{"email":"3fddac958924aef220f202ca567388ddab3f14a8@infradead.org","name":"Peter Zijlstra"},"message":"sched: Move wait.c into kernel/sched/\n\nSuggested-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Andrew Morton <akpm@linux-foundation.org>\nLink: http://lkml.kernel.org/n/tip-5q5yqvdaen0rmapwloeaotx3@git.kernel.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\n[rameezmustafa@codeaurora.org: Port to msm-3.10]\nSigned-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/e79f8e6d4beea7ef6fa2ed52a96e6e3f4274bc94"},{"sha":"34c33b1e582f95633d3e9946983c3b8b166995be","author":{"email":"872f71ea18f72c0748629a56d0a990d2fe86539f@gmail.com","name":"f100cleveland"},"message":"sched/deadline: Add SCHED_DEADLINE structures & implementation\n\nIntroduces the data structures, constants and symbols needed for\nSCHED_DEADLINE implementation.\n\nCore data structure of SCHED_DEADLINE are defined, along with their\ninitializers. Hooks for checking if a task belong to the new policy\nare also added where they are needed.\n\nAdds a scheduling class, in sched/dl.c and a new policy called\nSCHED_DEADLINE. It is an implementation of the Earliest Deadline\nFirst (EDF) scheduling algorithm, augmented with a mechanism (called\nConstant Bandwidth Server, CBS) that makes it possible to isolate\nthe behaviour of tasks between each other.\n\nThe typical -deadline task will be made up of a computation phase\n(instance) which is activated on a periodic or sporadic fashion. The\nexpected (maximum) duration of such computation is called the task's\nruntime; the time interval by which each instance need to be completed\nis called the task's relative deadline. The task's absolute deadline\nis dynamically calculated as the time instant a task (better, an\ninstance) activates plus the relative deadline.\n\nThe EDF algorithms selects the task with the smallest absolute\ndeadline as the one to be executed first, while the CBS ensures each\ntask to run for at most its runtime every (relative) deadline\nlength time interval, avoiding any interference between different\ntasks (bandwidth isolation).\nThanks to this feature, also tasks that do not strictly comply with\nthe computational model sketched above can effectively use the new\npolicy.\n\nTo summarize, this patch:\n - introduces the data structures, constants and symbols needed;\n - implements the core logic of the scheduling algorithm in the new\n   scheduling class file;\n - provides all the glue code between the new scheduling class and\n   the core scheduler and refines the interactions between sched/dl\n   and the other existing scheduling classes.\n\nSigned-off-by: Dario Faggioli <raistlin@linux.it>\nSigned-off-by: Michael Trimarchi <michael@amarulasolutions.com>\nSigned-off-by: Fabio Checconi <fchecconi@gmail.com>\nSigned-off-by: Juri Lelli <juri.lelli@gmail.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1383831828-15501-4-git-send-email-juri.lelli@gmail.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\n[rameezmustafa@codeaurora.org: Port to msm-3.10]\nSigned-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/34c33b1e582f95633d3e9946983c3b8b166995be"},{"sha":"b5ebfc5d14202ab68a53106a53bae565000dadac","author":{"email":"bdc6bcd4e8b34b4b92413d758024aeca6da0e459@gmail.com","name":"Juri Lelli"},"message":"sched/deadline: Add SCHED_DEADLINE SMP-related data structures & logic\n\nIntroduces data structures relevant for implementing dynamic\nmigration of -deadline tasks and the logic for checking if\nrunqueues are overloaded with -deadline tasks and for choosing\nwhere a task should migrate, when it is the case.\n\nAdds also dynamic migrations to SCHED_DEADLINE, so that tasks can\nbe moved among CPUs when necessary. It is also possible to bind a\ntask to a (set of) CPU(s), thus restricting its capability of\nmigrating, or forbidding migrations at all.\n\nThe very same approach used in sched_rt is utilised:\n - -deadline tasks are kept into CPU-specific runqueues,\n - -deadline tasks are migrated among runqueues to achieve the\n   following:\n    * on an M-CPU system the M earliest deadline ready tasks\n      are always running;\n    * affinity/cpusets settings of all the -deadline tasks is\n      always respected.\n\nTherefore, this very special form of \"load balancing\" is done with\nan active method, i.e., the scheduler pushes or pulls tasks between\nrunqueues when they are woken up and/or (de)scheduled.\nIOW, every time a preemption occurs, the descheduled task might be sent\nto some other CPU (depending on its deadline) to continue executing\n(push). On the other hand, every time a CPU becomes idle, it might pull\nthe second earliest deadline ready task from some other CPU.\n\nTo enforce this, a pull operation is always attempted before taking any\nscheduling decision (pre_schedule()), as well as a push one after each\nscheduling decision (post_schedule()). In addition, when a task arrives\nor wakes up, the best CPU where to resume it is selected taking into\naccount its affinity mask, the system topology, but also its deadline.\nE.g., from the scheduling point of view, the best CPU where to wake\nup (and also where to push) a task is the one which is running the task\nwith the latest deadline among the M executing ones.\n\nIn order to facilitate these decisions, per-runqueue \"caching\" of the\ndeadlines of the currently running and of the first ready task is used.\nQueued but not running tasks are also parked in another rb-tree to\nspeed-up pushes.\n\nSigned-off-by: Juri Lelli <juri.lelli@gmail.com>\nSigned-off-by: Dario Faggioli <raistlin@linux.it>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1383831828-15501-5-git-send-email-juri.lelli@gmail.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\n[rameezmustafa@codeaurora.org: Port to msm-3.10]\nSigned-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/b5ebfc5d14202ab68a53106a53bae565000dadac"},{"sha":"6e53aceaefa3386171ce8838b93b4363d84cef7d","author":{"email":"d76701c8994d429ae27f3beb6ae5506d2b99b818@linux.it","name":"Dario Faggioli"},"message":"sched/deadline: Add SCHED_DEADLINE avg_update accounting\n\nMake the core scheduler and load balancer aware of the load\nproduced by -deadline tasks, by updating the moving average\nlike for sched_rt.\n\nSigned-off-by: Dario Faggioli <raistlin@linux.it>\nSigned-off-by: Juri Lelli <juri.lelli@gmail.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1383831828-15501-6-git-send-email-juri.lelli@gmail.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/6e53aceaefa3386171ce8838b93b4363d84cef7d"},{"sha":"1c18bc380b3139272ed323653a20d9a185b7b400","author":{"email":"406d52b13bb6f806338b12ff17037641fd1b3699@ericsson.com","name":"Harald Gustafsson"},"message":"sched/deadline: Add period support for SCHED_DEADLINE tasks\n\nMake it possible to specify a period (different or equal than\ndeadline) for -deadline tasks. Relative deadlines (D_i) are used on\ntask arrivals to generate new scheduling (absolute) deadlines as \"d =\nt + D_i\", and periods (P_i) to postpone the scheduling deadlines as \"d\n= d + P_i\" when the budget is zero.\n\nThis is in general useful to model (and schedule) tasks that have slow\nactivation rates (long periods), but have to be scheduled soon once\nactivated (short deadlines).\n\nSigned-off-by: Harald Gustafsson <harald.gustafsson@ericsson.com>\nSigned-off-by: Dario Faggioli <raistlin@linux.it>\nSigned-off-by: Juri Lelli <juri.lelli@gmail.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1383831828-15501-7-git-send-email-juri.lelli@gmail.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/1c18bc380b3139272ed323653a20d9a185b7b400"},{"sha":"36bf5190bf3100ee0d419e5955e124e34be155d2","author":{"email":"d76701c8994d429ae27f3beb6ae5506d2b99b818@linux.it","name":"Dario Faggioli"},"message":"sched/deadline: Add latency tracing for SCHED_DEADLINE tasks\n\nIt is very likely that systems that wants/needs to use the new\nSCHED_DEADLINE policy also want to have the scheduling latency of\nthe -deadline tasks under control.\n\nFor this reason a new version of the scheduling wakeup latency,\ncalled \"wakeup_dl\", is introduced.\n\nAs a consequence of applying this patch there will be three wakeup\nlatency tracer:\n\n * \"wakeup\", that deals with all tasks in the system;\n * \"wakeup_rt\", that deals with -rt and -deadline tasks only;\n * \"wakeup_dl\", that deals with -deadline tasks only.\n\nSigned-off-by: Dario Faggioli <raistlin@linux.it>\nSigned-off-by: Juri Lelli <juri.lelli@gmail.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1383831828-15501-9-git-send-email-juri.lelli@gmail.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/f100cleveland/saberCore64/commits/36bf5190bf3100ee0d419e5955e124e34be155d2"}]}