{"push_id":712483532,"size":195,"distinct_size":1,"ref":"refs/heads/topics/drivers/pc3x3-clk-drivers","head":"6f60511db3512599dc225a19c8d5f10f03e70c01","before":"0b713900656a3052cf0ef40e02eeb29034e8e2bb","commits":[{"sha":"14c3dec2a875d898262be79c0f85e5f2b70a71b0","author":{"email":"074881f6f5da4d3b5278870ff234d1077ee622c0@ezchip.com","name":"Chris Metcalf"},"message":"tile: modify arch_spin_unlock_wait() semantics\n\nRather than trying to wait until all possible lockers have\nunlocked the lock, we now only wait until the current locker\n(if any) has released the lock.\n\nThe old code was correct, but the new code works more like the x86\ncode and thus hopefully is more appropriate under contention.\nSee commit 78bff1c8684f (\"x86/ticketlock: Fix spin_unlock_wait()\nlivelock\") for x86.\n\nSigned-off-by: Chris Metcalf <cmetcalf@ezchip.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/14c3dec2a875d898262be79c0f85e5f2b70a71b0"},{"sha":"627ae54854edfbf29d5997015c190de22eef497f","author":{"email":"074881f6f5da4d3b5278870ff234d1077ee622c0@ezchip.com","name":"Chris Metcalf"},"message":"tile: use READ_ONCE() in arch_spin_is_locked()\n\nThis avoid potential issues if callers were to loop on these\nroutines without some kind of memory barrier.  Currently there\nare no such users in-tree, but it seems better safe than sorry.\n\nAlso, in the tilepro case we read \"current\" before \"next\",\nwhich gives us a slightly better guarantee that the lock was\nactually unlocked at least momentarily if we return claiming\nthat it is not locked.  None of the callers actually rely on\nthis behavior, as far as I know, however.\n\nSigned-off-by: Chris Metcalf <cmetcalf@ezchip.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/627ae54854edfbf29d5997015c190de22eef497f"},{"sha":"5bf6c07a1843813d0065feaaecba622d49148d7e","author":{"email":"074881f6f5da4d3b5278870ff234d1077ee622c0@ezchip.com","name":"Chris Metcalf"},"message":"tile: add <asm/word-at-a-time.h> and enable support functions\n\nThis change enables the generic strncpy_from_user() and strnlen_user()\nusing word-at-a-time.h.  The tile implementation is trivial since\nboth tilepro and tilegx have SIMD operations that do byte-wise\ncomparisons against immediate zero for each byte, and return an\n0x01 byte in each position where there is a 0x00 byte.\n\nSigned-off-by: Chris Metcalf <cmetcalf@ezchip.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/5bf6c07a1843813d0065feaaecba622d49148d7e"},{"sha":"b4287df82991ca608f44d7ac12ad9b3bc39d5baa","author":{"email":"074881f6f5da4d3b5278870ff234d1077ee622c0@ezchip.com","name":"Chris Metcalf"},"message":"drivers/tty/hvc/hvc_tile.c: properly return -EAGAIN\n\nWe were returning zero if no bytes could be written to the Tilera\nhypervisor console device, but this causes the output to be truncated.\nBy returning -EAGAIN the tty hvc driver will come back and try again,\nwhich gives the semantics we want, and avoids dropping console output.\n\nAcked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Chris Metcalf <cmetcalf@ezchip.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/b4287df82991ca608f44d7ac12ad9b3bc39d5baa"},{"sha":"e5701b74ccfdbbb0b4d9abcc7d0c569bf5e5375b","author":{"email":"074881f6f5da4d3b5278870ff234d1077ee622c0@ezchip.com","name":"Chris Metcalf"},"message":"tile: support delivering NMIs for multicore backtrace\n\nA new hypervisor service was added some time ago (MDE 4.2.1 or\nlater, or MDE 4.3 or later) that allows cores to request NMIs\nto be delivered to other cores.  Use this facility to deliver\na request that causes a backtrace to be generated on each core,\nand hook it into the magic SysRq functionality.\n\nSigned-off-by: Chris Metcalf <cmetcalf@ezchip.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/e5701b74ccfdbbb0b4d9abcc7d0c569bf5e5375b"},{"sha":"9a5d2cbe6a1623dadfd93007382b0d12d6bac894","author":{"email":"074881f6f5da4d3b5278870ff234d1077ee622c0@ezchip.com","name":"Chris Metcalf"},"message":"tile: set up initial stack top to honor STACK_TOP_DELTA\n\nFor some reason this was never changed to match the rest of the\ncode where we always initialize the kernel sp 64 bytes below\nthe top of the page.  This is generally harmless, but it does\nmean that if you do a dump_stack() early on in kernel boot you\nsee a bogus warning about stack overrun.\n\nSigned-off-by: Chris Metcalf <cmetcalf@ezchip.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/9a5d2cbe6a1623dadfd93007382b0d12d6bac894"},{"sha":"e8200baa2fd2e9c4bc7abd824a9e675d914e54a0","author":{"email":"074881f6f5da4d3b5278870ff234d1077ee622c0@ezchip.com","name":"Chris Metcalf"},"message":"tile: fix \"odd fault\" warning for stack backtraces\n\nWe were setting ex1 in new kernel threads to KERNEL_PL.\nBut since we just do a simple context-switch, not an iret,\nany value set here is ignored anyway, and its presence causes\nstack backtraces to end with a warning about an \"odd fault\".\n\nSigned-off-by: Chris Metcalf <cmetcalf@ezchip.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/e8200baa2fd2e9c4bc7abd824a9e675d914e54a0"},{"sha":"47ad7b9bbeaac34e43d9dc8db796f1f68194b9ad","author":{"email":"074881f6f5da4d3b5278870ff234d1077ee622c0@ezchip.com","name":"Chris Metcalf"},"message":"tile: improve stack backtrace\n\nThis commit fixes a number of issues with the tile backtrace code.\n\n- Don't try to identify userspace shared object or executable paths\n  if we are doing a backtrace from an interrupt; it's not legal,\n  and also unlikely to be interesting.  Likewise, don't try to do\n  it for other address spaces, since d_path() assumes it is being\n  called in \"current\" context.\n\n- Move \"in_backtrace\" from thread_struct to thread_info.\n  This way we can access it even if our stack thread_info has been\n  clobbered, which makes backtracing more robust.\n\n- Avoid using \"current\" directly when testing for is_sigreturn().\n  Since \"current\" may be corrupt, we're better off using kbt->task\n  explicitly to look up the vdso_base for the current task.\n  Conveniently, this simplifies the internal APIs (we only need\n  one is_sigreturn() function now).\n\n- Avoid bogus \"Odd fault\" warning when pc/sp/ex1 are all zero,\n  as is true for kernel threads above the last frame.\n\n- Hook into Tejun Heo's dump_stack() framework in lib/dump_stack.c.\n\n- Write last entry in save_stack_trace() as ULONG_MAX, not zero,\n  since ftrace (at least) relies on finding that marker.\n\n- Implement save_stack_trace_regs() and save_strack_trace_user(),\n  and set CONFIG_USER_STACKTRACE_SUPPORT.\n\nSigned-off-by: Chris Metcalf <cmetcalf@ezchip.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/47ad7b9bbeaac34e43d9dc8db796f1f68194b9ad"},{"sha":"248d200df34f3e44a4140f32dfc7428c52615332","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: fix, btrfs_release_super_kobj() should to clean up the kobject data\n\nThe following test case fails indicating that, thread tried to init an initialized object.\n\nkernel: [232104.016513] kobject (ffff880006c1c980): tried to init an initialized object, something is seriously wrong.\n\nbtrfs_sysfs_remove_one() self test code:\n\nopen_tree()\n{\n ::\n        ret = btrfs_sysfs_add_one(fs_info);\n\tif (ret) {\n              pr_err(\"BTRFS: failed to init sysfs interface: %d\\n\", ret);\n                goto fail_block_groups;\n        }\n+       btrfs_sysfs_remove_one(fs_info);\n+       ret = btrfs_sysfs_add_one(fs_info);\n+       if (ret) {\n+               pr_err(\"BTRFS: failed to init sysfs interface: %d\\n\", ret);\n+               goto fail_block_groups;\n+       }\n\ncleaning up the unregistered kobject fixes this.\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/248d200df34f3e44a4140f32dfc7428c52615332"},{"sha":"4e51f005a22a2c7795351b975437b0cee0acce3e","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: fix, fs_info kobject_unregister has init_completion() twice\n\nkobject_unregister is to handle the release of the kobject,\nits completion init is being called in btrfs_sysfs_add_one(),\nso we don't have to do the same in the open_ctree() again.\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/4e51f005a22a2c7795351b975437b0cee0acce3e"},{"sha":"e7e1aa9c913da380fbf1977ac4fa98e464023605","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: fix, undo sysfs device links\n\nTheoritically need to remove the device links attributes, but since its entire device\nkobject was removed, so there wasn't any issue of about it. Just do it nicely.\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/e7e1aa9c913da380fbf1977ac4fa98e464023605"},{"sha":"8345ea31dc6e1772726d1d0b8864dedac55038e0","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: fix, kobject pointer clean up needed after kobject release\n\nThe sysfs clean up self test like in the below code fails, since\nfs_info->device_dir_kobject still points to its stale kobject.\nReseting this pointer will help to fix this.\n\nopen_ctree()\n{\n\nret = btrfs_sysfs_add_one(fs_info);\n::\n+       btrfs_sysfs_remove_one(fs_info);\n+       ret = btrfs_sysfs_add_one(fs_info);\n+       if (ret) {\n+               pr_err(\"BTRFS: failed to init sysfs interface: %d\\n\", ret);\n+               goto fail_block_groups;\n+       }\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/8345ea31dc6e1772726d1d0b8864dedac55038e0"},{"sha":"4d435731f99db87020730c4b17e1da148908340e","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfc: sysfs: fix, check if device_dir_kobj is init before destroy\n\nSince the failure code in the btrfs_sysfs_add_one() can\ncall btrfs_sysfs_remove_one() even before device_dir_kobj\nhas been created we need to check if its null.\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/4d435731f99db87020730c4b17e1da148908340e"},{"sha":"aaf13305160490531b0d5ee4d56d32fc09f9bfa0","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: reorder the kobject creations\n\nAs of now the order in which the kobjects are created\nat btrfs_sysfs_add_one() is..\n fsid\n features\n unknown features (dynamic features)\n devices.\n\nSince we would move fsid and device kobject to fs_devices\nfrom fs_info structure, this patch will reorder in which\nthe kobjects are created as below.\n fsid\n devices\n features\n unknown features (dynamic features)\n\nAnd hence the btrfs_sysfs_remove_one() will follow the same\nin reverse order. and the device kobject destroy now can\nbe moved into the function __btrfs_sysfs_remove_one()\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/aaf13305160490531b0d5ee4d56d32fc09f9bfa0"},{"sha":"3a08f3b72a4f03e413d89d8505b17c05194e63f9","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: rename __btrfs_sysfs_remove_one to btrfs_sysfs_remove_fsid\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/3a08f3b72a4f03e413d89d8505b17c05194e63f9"},{"sha":"720592157eeef627ff9a7c7c55ab1713bc48fb50","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: introduce function btrfs_sysfs_add_fsid() to create sysfs fsid\n\nWe need it in a seperate function so that it can be called from the\ndevice discovery thread as well.\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/720592157eeef627ff9a7c7c55ab1713bc48fb50"},{"sha":"0dd2906f7229186424cdc80be8654b2c21d9c04c","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: let default_attrs be separate from the kset\n\nAs of now btrfs_attrs are provided using the default_attrs through\nthe kset. Separate them and create the default_attrs using the\nsysfs_create_files instead. By doing this we will have the\nflexibility that device discovery thread could create fsid\nkobject.\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/0dd2906f7229186424cdc80be8654b2c21d9c04c"},{"sha":"00c921c23f9155597ff4ac1263a6ff46dc9e2206","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: separate device kobject and its attribute creation\n\nSeparate device kobject and its attribute creation so that device\nkobject can be created from the device discovery thread.\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/00c921c23f9155597ff4ac1263a6ff46dc9e2206"},{"sha":"2e7910d6ca359ff1dbe05b74e3d7f353b5b65362","author":{"email":"720fab3a919e9ecd827b8ea6d06ecf062751adf6@oracle.com","name":"Anand Jain"},"message":"Btrfs: sysfs: move super_kobj and device_dir_kobj from fs_info to btrfs_fs_devices\n\nThis patch will provide a framework and help to create attributes\nfrom the structure btrfs_fs_devices which are available even before\nfs_info is created. So by moving the parent kobject super_kobj from\nfs_info to btrfs_fs_devices, it will help to create attributes\nfrom the btrfs_fs_devices as well.\n\nPatches on top of this patch now will be able to create the\nsys/fs/btrfs/fsid kobject and attributes from btrfs_fs_devices\nwhen devices are scanned and registered to the kernel.\n\nJust to note, this does not change any of the existing btrfs sysfs\nexternal kobject names and its attributes and not even the life\ncycle of them. Changes are internal only. And to ensure the same,\nthis path has been tested with various device operations and,\nchecking and comparing the sysfs kobjects and attributes with\nsysfs kobject and attributes with out this patch, and they remain\nsame.\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/2e7910d6ca359ff1dbe05b74e3d7f353b5b65362"},{"sha":"c73eccf75bf92e49be30884da32a169b04eb5bc9","author":{"email":"81069a49b521acf79f562d472ec8c4e0d6a88433@oracle.com","name":"Anand Jain"},"message":"Btrfs: introduce btrfs_get_fs_uuids to get fs_uuids\n\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/c73eccf75bf92e49be30884da32a169b04eb5bc9"}]}