{"action":"opened","issue":{"url":"https://api.github.com/repos/zephyrproject-rtos/zephyr/issues/7193","repository_url":"https://api.github.com/repos/zephyrproject-rtos/zephyr","labels_url":"https://api.github.com/repos/zephyrproject-rtos/zephyr/issues/7193/labels{/name}","comments_url":"https://api.github.com/repos/zephyrproject-rtos/zephyr/issues/7193/comments","events_url":"https://api.github.com/repos/zephyrproject-rtos/zephyr/issues/7193/events","html_url":"https://github.com/zephyrproject-rtos/zephyr/issues/7193","id":317752213,"number":7193,"title":"tickless and timeslicing don't play well together","user":{"login":"andyross","id":300115,"avatar_url":"https://avatars1.githubusercontent.com/u/300115?v=4","gravatar_id":"","url":"https://api.github.com/users/andyross","html_url":"https://github.com/andyross","followers_url":"https://api.github.com/users/andyross/followers","following_url":"https://api.github.com/users/andyross/following{/other_user}","gists_url":"https://api.github.com/users/andyross/gists{/gist_id}","starred_url":"https://api.github.com/users/andyross/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andyross/subscriptions","organizations_url":"https://api.github.com/users/andyross/orgs","repos_url":"https://api.github.com/users/andyross/repos","events_url":"https://api.github.com/users/andyross/events{/privacy}","received_events_url":"https://api.github.com/users/andyross/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-25T18:55:29Z","updated_at":"2018-04-25T18:55:29Z","closed_at":null,"author_association":"COLLABORATOR","body":"Specific bug: wake up a thread (or create a new one) at the same priority as the currently running thread, both of which are at the same preemptible priority and in a situation where no other threads exist at that priority.  In theory, the CPU timer should be adjusted to reflect the new situation and expire in one slicing tick.  In practice, the timer is not adjusted and the new thread won't get any CPU until whenever the next interrupt fires, which could be a long time.\r\n\r\nThat issue was found via inspection as I stumpled over this code while working on the scheduler.  The more general problem is that we have pretty poor test coverage for both timeslicing and tickless behaviors, this situation needs to be tested and handled, along with (probably) others."}}
{"actor":{"display_login":"andyross"}}