{"action":"created","issue":{"url":"https://api.github.com/repos/opensocdebug/documentation/issues/1","labels_url":"https://api.github.com/repos/opensocdebug/documentation/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/opensocdebug/documentation/issues/1/comments","events_url":"https://api.github.com/repos/opensocdebug/documentation/issues/1/events","html_url":"https://github.com/opensocdebug/documentation/issues/1","id":126477770,"number":1,"title":"Notion of a Global Clock","user":{"login":"wallento","id":299017,"avatar_url":"https://avatars.githubusercontent.com/u/299017?v=3","gravatar_id":"","url":"https://api.github.com/users/wallento","html_url":"https://github.com/wallento","followers_url":"https://api.github.com/users/wallento/followers","following_url":"https://api.github.com/users/wallento/following{/other_user}","gists_url":"https://api.github.com/users/wallento/gists{/gist_id}","starred_url":"https://api.github.com/users/wallento/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wallento/subscriptions","organizations_url":"https://api.github.com/users/wallento/orgs","repos_url":"https://api.github.com/users/wallento/repos","events_url":"https://api.github.com/users/wallento/events{/privacy}","received_events_url":"https://api.github.com/users/wallento/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-01-13T18:04:13Z","updated_at":"2016-01-14T10:36:43Z","closed_at":null,"body":"We need a flexible way to have a global clock to send timestamps with the trace events.\r\n\r\nProposal: (Re-)Use a global time stamp provider as in OpTiMSoC, but allow to register slice it for better distribution on the chip. Each module then gets a parameter TIMESTAMP_DELAY, that can be read as a configuration register by the software and timestamps are accordingly adjusted."},"comment":{"url":"https://api.github.com/repos/opensocdebug/documentation/issues/comments/171603979","html_url":"https://github.com/opensocdebug/documentation/issues/1#issuecomment-171603979","issue_url":"https://api.github.com/repos/opensocdebug/documentation/issues/1","id":171603979,"user":{"login":"wsong83","id":821840,"avatar_url":"https://avatars.githubusercontent.com/u/821840?v=3","gravatar_id":"","url":"https://api.github.com/users/wsong83","html_url":"https://github.com/wsong83","followers_url":"https://api.github.com/users/wsong83/followers","following_url":"https://api.github.com/users/wsong83/following{/other_user}","gists_url":"https://api.github.com/users/wsong83/gists{/gist_id}","starred_url":"https://api.github.com/users/wsong83/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wsong83/subscriptions","organizations_url":"https://api.github.com/users/wsong83/orgs","repos_url":"https://api.github.com/users/wsong83/repos","events_url":"https://api.github.com/users/wsong83/events{/privacy}","received_events_url":"https://api.github.com/users/wsong83/received_events","type":"User","site_admin":false},"created_at":"2016-01-14T10:36:43Z","updated_at":"2016-01-14T10:36:43Z","body":"How accurate is this clock or time stamp?\r\nThere is a time CSR defined as the wall clock which is shared by all cores.\r\nIt works like a RTC.\r\nHowever, the update of this time CSR is not frequent.\r\nWhat I understand RISC-V suggests automatic update in every 100ns to even 1us.\r\nThen it is also possible to deliberately read (with delay overhead) the remote RTC and update local time CSR when reading this CSR (using the CSR read instruction).\r\nThe local timecmp interrupt is compared against local time rather than the remote RTC value.\r\nIs this the same clock you want?"}}