{"push_id":2713337152,"size":13,"distinct_size":13,"ref":"refs/heads/master","head":"33dab4725f8adb17642509a5db3e44c4cf81dd7c","before":"d7d9e6b0e664d0186c760f6c8ec4621914952b3b","commits":[{"sha":"1848bb29f1ef74750acccce175f8fbe469448f21","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Add thread to execute handlers for asynchronous signals [win64amd]\n\nAdded asynchSignalReporterThread to execute handlers\n(J9WinAMD64AsyncHandlerRecord->handler) for asynchronous signals.\n\nasynchSignalReporterThread is initialized/created within\ninitializeSignalTools.\n\nasynchSignalReporter represents the main body of\nasynchSignalReporterThread. Currently, it is a stub which sets the\nthread's name and executes the thread exit code. The main functionality\nof asynchSignalReporter will be added later once required dependencies\nhave been introduced.\nCode related to asynchSignalReporterThread is wrapped with\nOMR_PORT_ASYNC_HANDLER flag (similar to the unix implementation).\n\nomrutil.h has the prototype for createThreadWithCategory.\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/1848bb29f1ef74750acccce175f8fbe469448f21"},{"sha":"c26f048dbb7f2942d9acaa6237fb44d37e782142","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Add registerMasterHandlers [win64amd]\n\nregisterMasterHandlers registers a master signal handler for the signals\nspecified in flags.\n\nCurrently, win64amd only has a master signal handler for asynchronous\nsignals: masterASynchSignalHandler. So, registerMasterHandlers only\nsupports masterASynchSignalHandler (OMRPORT_SIG_FLAG_SIGALLASYNC).\nOMRPORT_SIG_FLAG_SIGALLSYNC is not supported on win64amd.\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/c26f048dbb7f2942d9acaa6237fb44d37e782142"},{"sha":"823add1ddae06c4929bfee84e06e42420752073c","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Add asyncReporterShutdownMonitor [win64amd]\n\nasyncReporterShutdownMonitor will be used to synchronize shutdown of\nasynchSignalReporterThread.\n\ninitializeSignalTools updated to initialize\nasyncReporterShutdownMonitor, and destroySignalTools updated to destroy\nasyncReporterShutdownMonitor.\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/823add1ddae06c4929bfee84e06e42420752073c"},{"sha":"c96d6ff726e434c090c3d6ade46e0be37edd66a0","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Add runHandlers [win64amd]\n\nrunHandlers executes the associated handlers stored within\nasyncHandlerList for a a port library signal flag. It will be used to\ninvoke asynchronous handlers from asynchSignalReporter (main body of\nasynchSignalReporterThread).\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/c96d6ff726e434c090c3d6ade46e0be37edd66a0"},{"sha":"3b35730d2ca8a01c5e6e6bbdfb8abee830f41980","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Implement asynchSignalReporter [win64amd]\n\nPreviously, only a stub existed for asynchSignalReporter. An\nimplementation for asynchSignalReporter is added. asynchSignalReporter\nexecutes handlers associated to pending signals (signalCounts[...]). It\nreceives notification of a signal via a j9sem_post (from\nmasterASynchSignalHandler). For thread shutdown,\nasyncReporterShutdownMonitor is used.\n\nshutDownASynchReporter is used to indicate start and end of\nasynchSignalReporterThread termination.\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/3b35730d2ca8a01c5e6e6bbdfb8abee830f41980"},{"sha":"c26c9fef54eb94e7f0a0f109f23a15aa6605b87b","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Terminate asynchSignalReporterThread in sig_full_shutdown [win64amd]\n\nAdded code to terminate asynchSignalReporterThread in sig_full_shutdown.\nsig_full_shutdown waits until asynchSignalReporterThread is terminated.\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/c26c9fef54eb94e7f0a0f109f23a15aa6605b87b"},{"sha":"141239731d0c5f15237db794a794305e86ab7de1","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Fix omrsig_set_async_signal_handler [win64amd]\n\ni) Properly initialize variables during declaration.\n\nii) Add trace points.\n\niii) For the specified port library signal flags, register master\nasynchronous handler (masterASynchSignalHandler) with the OS.\n\niv) Currently, J9WinAMD64AsyncHandlerRecord->flags is assigned a new\nvalue which removes previous signal/handler relations. This is incorrect\nand inconsistent with the Unix implementation. When associating signals\nwith existing handlers, J9WinAMD64AsyncHandlerRecord->flags must be\nupdated using a bit-wise OR so that previous signal/handler relations\nare not impacted.\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/141239731d0c5f15237db794a794305e86ab7de1"},{"sha":"f19a26a39311324573abd83bd0942878d59e26fd","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Add implementation of omrsig_set_single_async_signal_handler [win64amd]\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/f19a26a39311324573abd83bd0942878d59e26fd"},{"sha":"d1341bfb45db980d6a3c022a9e83b86b4f3d2d68","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Update consoleCtrlHandler [win64amd]\n\nconsoleCtrlHandler is a HandlerRoutine, and it is responsible for\nhandling control events.\n\ni) consoleCtrlHandler only handled three control events. Now,\nconsoleCtrlHandler handles all five control events: CTRL_BREAK_EVENT is\ntranslated to SIGBREAK, CTRL_C_EVENT is translated to SIGINT,\nCTRL_CLOSE_EVENT/CTRL_LOGOFF_EVENT/CTRL_SHUTDOWN_EVENT are translated to\nSIGTERM.\n\nii) Before, consoleCtrlHandler invoked the handlers. Now,\nconsoleCtrlHandler only increments counters (signalCounts[...]) for\nunprocessed signals, and notifies the asynchSignalReporterThread.\n\niii) consoleCtrlHandler (HandlerRoutine) won't be invoked for a signal\nsend using the raise(...) function. In case of raise(...), the signal\nhandler registered with the OS using signal(...) will be invoked. So,\nconsoleCtrlHandler mustn't be used to invoke\nJ9WinAMD64AsyncHandlerRecord->handler(s). Now,\nasynchSignalReporterThread is responsible for invoking\nJ9WinAMD64AsyncHandlerRecord->handler(s).\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/d1341bfb45db980d6a3c022a9e83b86b4f3d2d68"},{"sha":"a203762854050c1c057df31d5dafcdcd89200c23","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Add setReporterPriority [win64amd]\n\nsetReporterPriority sets the thread priority for\nasynchSignalReporterThread.\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/a203762854050c1c057df31d5dafcdcd89200c23"},{"sha":"e1ed77aa7586bf5f5cb11be9c42ae13209a54545","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Update omrsig_set_reporter_priority [win64amd]\n\nasynchSignalReporterThread has been added on win64amd. So,\nomrsig_set_reporter_priority is updated to set the priority of\nasynchSignalReporterThread.\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/e1ed77aa7586bf5f5cb11be9c42ae13209a54545"},{"sha":"493fd3e15ec7e0057e05b4f4cad0d22ab026fad6","author":{"name":"Babneet Singh","email":"8abd1ff3f747df23e2285ffa6b8768f665774ab2@ca.ibm.com"},"message":"Replace SIGQUIT with SIGBREAK [win32]\n\nCurrently, the SIGQUIT flag is used for SIGBREAK on Windows. This is\nconfusing since SIGQUIT doesn't exist on Windows.\n\nA unique SIGBREAK flag has been added on Windows. So, the SIGQUIT flag\nis replaced with the new SIGBREAK flag.\n\nSigned-off-by: Babneet Singh <sbabneet@ca.ibm.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/493fd3e15ec7e0057e05b4f4cad0d22ab026fad6"},{"sha":"33dab4725f8adb17642509a5db3e44c4cf81dd7c","author":{"name":"Charlie Gracie","email":"c8b9d2817b7b72c60472f4c12fdff6d44dcf9f2c@gmail.com"},"message":"Merge pull request #2716 from babsingh/signal_minimal_windows_v3\n\nMinimal Signal Changes Part 3 [win64amd]","distinct":true,"url":"https://api.github.com/repos/eclipse/omr/commits/33dab4725f8adb17642509a5db3e44c4cf81dd7c"}]}
{"actor":{"display_login":"charliegracie"}}