{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":51007072,"defaultBranch":"master","name":"xen","ownerLogin":"xen-project","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2016-02-03T15:00:09.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/17047965?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1714728396.0","currentOid":""},"activityList":{"items":[{"before":"6d41f5b9e112e8934f59edfd7168a36706e0341a","after":"08f9b1dd9c9435d4cca006e43917245710b39be3","ref":"refs/heads/master","pushedAt":"2024-06-29T05:54:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"MAINTAINERS: Step down as maintainer and committer\n\nRemain a Reviewer on the golang bindings and scheduler for now (using\na xenproject.org alias), since there may be architectural decisions I\ncan shed light on.\n\nRemove the XENTRACE section entirely, as there's no obvious candidate\nto take it over; having the respective parts fall back to the tools\nand The Rest seems the most reasonable option.\n\nSigned-off-by: George Dunlap \nAcked-by: Stefano Stabellini \nAcked-by: Juergen Gross \nAcked-by: Bertrand Marquis ","shortMessageHtmlLink":"MAINTAINERS: Step down as maintainer and committer"}},{"before":"402e473249cf62dd4c6b3b137aa845db0fe1453a","after":"6d41f5b9e112e8934f59edfd7168a36706e0341a","ref":"refs/heads/master","pushedAt":"2024-06-28T21:14:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"automation/eclair: add deviations agreed in MISRA meetings\n\nUpdate ECLAIR configuration to take into account the deviations\nagreed during the MISRA meetings.\n\nWhile doing this, remove the obsolete \"Set [123]\" comments.\n\nSigned-off-by: Federico Serafini \nReviewed-by: Stefano Stabellini \nRelease-Acked-By: Oleksii Kurochko ","shortMessageHtmlLink":"automation/eclair: add deviations agreed in MISRA meetings"}},{"before":"6d41f5b9e112e8934f59edfd7168a36706e0341a","after":"08f9b1dd9c9435d4cca006e43917245710b39be3","ref":"refs/heads/smoke","pushedAt":"2024-06-28T19:04:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"MAINTAINERS: Step down as maintainer and committer\n\nRemain a Reviewer on the golang bindings and scheduler for now (using\na xenproject.org alias), since there may be architectural decisions I\ncan shed light on.\n\nRemove the XENTRACE section entirely, as there's no obvious candidate\nto take it over; having the respective parts fall back to the tools\nand The Rest seems the most reasonable option.\n\nSigned-off-by: George Dunlap \nAcked-by: Stefano Stabellini \nAcked-by: Juergen Gross \nAcked-by: Bertrand Marquis ","shortMessageHtmlLink":"MAINTAINERS: Step down as maintainer and committer"}},{"before":"6d41f5b9e112e8934f59edfd7168a36706e0341a","after":"08f9b1dd9c9435d4cca006e43917245710b39be3","ref":"refs/heads/staging","pushedAt":"2024-06-28T14:44:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"MAINTAINERS: Step down as maintainer and committer\n\nRemain a Reviewer on the golang bindings and scheduler for now (using\na xenproject.org alias), since there may be architectural decisions I\ncan shed light on.\n\nRemove the XENTRACE section entirely, as there's no obvious candidate\nto take it over; having the respective parts fall back to the tools\nand The Rest seems the most reasonable option.\n\nSigned-off-by: George Dunlap \nAcked-by: Stefano Stabellini \nAcked-by: Juergen Gross \nAcked-by: Bertrand Marquis ","shortMessageHtmlLink":"MAINTAINERS: Step down as maintainer and committer"}},{"before":"ecadd22a3de8ce7f1799e85af6f1e37c06c57049","after":"402e473249cf62dd4c6b3b137aa845db0fe1453a","ref":"refs/heads/master","pushedAt":"2024-06-28T07:48:37.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"x86/traps: address violations of MISRA C Rule 20.7\n\nMISRA C Rule 20.7 states: \"Expressions resulting from the expansion\nof macro parameters shall be enclosed in parentheses\". Therefore, some\nmacro definitions should gain additional parentheses to ensure that all\ncurrent and future users will be safe with respect to expansions that\ncan possibly alter the semantics of the passed-in macro parameter.\n\nNo functional change.\n\nSigned-off-by: Nicola Vetrini \nReviewed-by: Stefano Stabellini \nAcked-by: Jan Beulich \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"x86/traps: address violations of MISRA C Rule 20.7"}},{"before":"402e473249cf62dd4c6b3b137aa845db0fe1453a","after":"6d41f5b9e112e8934f59edfd7168a36706e0341a","ref":"refs/heads/smoke","pushedAt":"2024-06-28T04:20:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"automation/eclair: add deviations agreed in MISRA meetings\n\nUpdate ECLAIR configuration to take into account the deviations\nagreed during the MISRA meetings.\n\nWhile doing this, remove the obsolete \"Set [123]\" comments.\n\nSigned-off-by: Federico Serafini \nReviewed-by: Stefano Stabellini \nRelease-Acked-By: Oleksii Kurochko ","shortMessageHtmlLink":"automation/eclair: add deviations agreed in MISRA meetings"}},{"before":"402e473249cf62dd4c6b3b137aa845db0fe1453a","after":"6d41f5b9e112e8934f59edfd7168a36706e0341a","ref":"refs/heads/staging","pushedAt":"2024-06-27T23:34:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"automation/eclair: add deviations agreed in MISRA meetings\n\nUpdate ECLAIR configuration to take into account the deviations\nagreed during the MISRA meetings.\n\nWhile doing this, remove the obsolete \"Set [123]\" comments.\n\nSigned-off-by: Federico Serafini \nReviewed-by: Stefano Stabellini \nRelease-Acked-By: Oleksii Kurochko ","shortMessageHtmlLink":"automation/eclair: add deviations agreed in MISRA meetings"}},{"before":"ecadd22a3de8ce7f1799e85af6f1e37c06c57049","after":"402e473249cf62dd4c6b3b137aa845db0fe1453a","ref":"refs/heads/smoke","pushedAt":"2024-06-27T14:54:37.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"x86/traps: address violations of MISRA C Rule 20.7\n\nMISRA C Rule 20.7 states: \"Expressions resulting from the expansion\nof macro parameters shall be enclosed in parentheses\". Therefore, some\nmacro definitions should gain additional parentheses to ensure that all\ncurrent and future users will be safe with respect to expansions that\ncan possibly alter the semantics of the passed-in macro parameter.\n\nNo functional change.\n\nSigned-off-by: Nicola Vetrini \nReviewed-by: Stefano Stabellini \nAcked-by: Jan Beulich \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"x86/traps: address violations of MISRA C Rule 20.7"}},{"before":"4712e3b3769e6c03e0aaaa8179395f0fb7b141cc","after":"ecadd22a3de8ce7f1799e85af6f1e37c06c57049","ref":"refs/heads/master","pushedAt":"2024-06-27T13:10:37.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"CHANGELOG: Add entries related to tracing\n\nSigned-off-by: George Dunlap \nAcked-by: Andrew Cooper \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"CHANGELOG: Add entries related to tracing"}},{"before":"ecadd22a3de8ce7f1799e85af6f1e37c06c57049","after":"402e473249cf62dd4c6b3b137aa845db0fe1453a","ref":"refs/heads/staging","pushedAt":"2024-06-27T11:52:37.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"x86/traps: address violations of MISRA C Rule 20.7\n\nMISRA C Rule 20.7 states: \"Expressions resulting from the expansion\nof macro parameters shall be enclosed in parentheses\". Therefore, some\nmacro definitions should gain additional parentheses to ensure that all\ncurrent and future users will be safe with respect to expansions that\ncan possibly alter the semantics of the passed-in macro parameter.\n\nNo functional change.\n\nSigned-off-by: Nicola Vetrini \nReviewed-by: Stefano Stabellini \nAcked-by: Jan Beulich \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"x86/traps: address violations of MISRA C Rule 20.7"}},{"before":"853f707cd9e2eb9410dbfbadbd5a01ac0252ef83","after":"4712e3b3769e6c03e0aaaa8179395f0fb7b141cc","ref":"refs/heads/master","pushedAt":"2024-06-27T04:04:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"Config.mk: update MiniOS commit\n\nPull in the gcc14 build fix there.\n\nSigned-off-by: Jan Beulich \nReviewed-by: Juergen Gross \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"Config.mk: update MiniOS commit"}},{"before":"3c7c9225ffa5605bf0603f9dd1666f3f786e2c44","after":"87a49d2ec6fe2881e4b0947ea3e0e0f041dc6be3","ref":"refs/heads/stable-4.17","pushedAt":"2024-06-26T23:44:36.000Z","pushType":"push","commitsCount":16,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"x86/irq: forward pending interrupts to new destination in fixup_irqs()\n\nfixup_irqs() is used to evacuate interrupts from to be offlined CPUs. Given\nthe CPU is to become offline, the normal migration logic used by Xen where the\nvector in the previous target(s) is left configured until the interrupt is\nreceived on the new destination is not suitable.\n\nInstead attempt to do as much as possible in order to prevent loosing\ninterrupts. If fixup_irqs() is called from the CPU to be offlined (as is\ncurrently the case for CPU hot unplug) attempt to forward pending vectors when\ninterrupts that target the current CPU are migrated to a different destination.\n\nAdditionally, for interrupts that have already been moved from the current CPU\nprior to the call to fixup_irqs() but that haven't been delivered to the new\ndestination (iow: interrupts with move_in_progress set and the current CPU set\nin ->arch.old_cpu_mask) also check whether the previous vector is pending and\nforward it to the new destination.\n\nThis allows us to remove the window with interrupts enabled at the bottom of\nfixup_irqs(). Such window wasn't safe anyway: references to the CPU to become\noffline are removed from interrupts masks, but the per-CPU vector_irq[] array\nis not updated to reflect those changes (as the CPU is going offline anyway).\n\nSigned-off-by: Roger Pau Monné \nReviewed-by: Jan Beulich \nmaster commit: e2bb28d621584fce15c907002ddc7c6772644b64\nmaster date: 2024-06-20 12:09:32 +0200","shortMessageHtmlLink":"x86/irq: forward pending interrupts to new destination in fixup_irqs()"}},{"before":"dde20e47afb51404d59be492ca924704f0fbf71d","after":"ecadd22a3de8ce7f1799e85af6f1e37c06c57049","ref":"refs/heads/smoke","pushedAt":"2024-06-26T22:26:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"CHANGELOG: Add entries related to tracing\n\nSigned-off-by: George Dunlap \nAcked-by: Andrew Cooper \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"CHANGELOG: Add entries related to tracing"}},{"before":"01f7a3c792241d348a4e454a30afdf6c0d6cd71c","after":"e95d30f9e5eed0c5d9dbf72d4cc3ae373152ab10","ref":"refs/heads/stable-4.18","pushedAt":"2024-06-26T21:08:37.000Z","pushType":"push","commitsCount":16,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"x86/irq: forward pending interrupts to new destination in fixup_irqs()\n\nfixup_irqs() is used to evacuate interrupts from to be offlined CPUs. Given\nthe CPU is to become offline, the normal migration logic used by Xen where the\nvector in the previous target(s) is left configured until the interrupt is\nreceived on the new destination is not suitable.\n\nInstead attempt to do as much as possible in order to prevent loosing\ninterrupts. If fixup_irqs() is called from the CPU to be offlined (as is\ncurrently the case for CPU hot unplug) attempt to forward pending vectors when\ninterrupts that target the current CPU are migrated to a different destination.\n\nAdditionally, for interrupts that have already been moved from the current CPU\nprior to the call to fixup_irqs() but that haven't been delivered to the new\ndestination (iow: interrupts with move_in_progress set and the current CPU set\nin ->arch.old_cpu_mask) also check whether the previous vector is pending and\nforward it to the new destination.\n\nThis allows us to remove the window with interrupts enabled at the bottom of\nfixup_irqs(). Such window wasn't safe anyway: references to the CPU to become\noffline are removed from interrupts masks, but the per-CPU vector_irq[] array\nis not updated to reflect those changes (as the CPU is going offline anyway).\n\nSigned-off-by: Roger Pau Monné \nReviewed-by: Jan Beulich \nmaster commit: e2bb28d621584fce15c907002ddc7c6772644b64\nmaster date: 2024-06-20 12:09:32 +0200","shortMessageHtmlLink":"x86/irq: forward pending interrupts to new destination in fixup_irqs()"}},{"before":"4712e3b3769e6c03e0aaaa8179395f0fb7b141cc","after":"dde20e47afb51404d59be492ca924704f0fbf71d","ref":"refs/heads/smoke","pushedAt":"2024-06-26T18:58:36.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"tools/xenalyze: Remove argp_program_bug_address\n\nxenalyze sets argp_program_bug_address to my old Citrix address. This\nwas done before xenalyze was in the xen.git tree; and it's the only\nprogram in the tree which does so.\n\nNow that xenalyze is part of the normal Xen distribution, it should be\nobvious where to report bugs.\n\nSigned-off-by: George Dunlap \nAcked-by: Andrew Cooper \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"tools/xenalyze: Remove argp_program_bug_address"}},{"before":"dde20e47afb51404d59be492ca924704f0fbf71d","after":"ecadd22a3de8ce7f1799e85af6f1e37c06c57049","ref":"refs/heads/staging","pushedAt":"2024-06-26T15:30:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"CHANGELOG: Add entries related to tracing\n\nSigned-off-by: George Dunlap \nAcked-by: Andrew Cooper \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"CHANGELOG: Add entries related to tracing"}},{"before":"853f707cd9e2eb9410dbfbadbd5a01ac0252ef83","after":"4712e3b3769e6c03e0aaaa8179395f0fb7b141cc","ref":"refs/heads/smoke","pushedAt":"2024-06-26T14:38:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"Config.mk: update MiniOS commit\n\nPull in the gcc14 build fix there.\n\nSigned-off-by: Jan Beulich \nReviewed-by: Juergen Gross \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"Config.mk: update MiniOS commit"}},{"before":"11ea49a3fda5f0cbd8546ee8bdc5e9c55736c828","after":"853f707cd9e2eb9410dbfbadbd5a01ac0252ef83","ref":"refs/heads/master","pushedAt":"2024-06-26T13:46:37.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"automation/eclair_analysis: deviate and|or|xor|not for MISRA C Rule 21.2\n\nRule 21.2 reports identifiers reserved for the C and POSIX standard\nlibraries: or, and, not and xor are reserved identifiers because they\nconstitute alternate spellings for the corresponding operators (they are\ndefined as macros by iso646.h); however Xen doesn't use standard library\nheaders, so there is no risk of overlap.\n\nThis addresses violations arising from x86_emulate/x86_emulate.c, where\nlabel statements named as or, and and xor appear.\n\nNo functional change.\n\nSigned-off-by: Alessandro Zucchelli \nAcked-by: Stefano Stabellini \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"automation/eclair_analysis: deviate and|or|xor|not for MISRA C Rule 21.2"}},{"before":"4712e3b3769e6c03e0aaaa8179395f0fb7b141cc","after":"dde20e47afb51404d59be492ca924704f0fbf71d","ref":"refs/heads/staging","pushedAt":"2024-06-26T13:46:37.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"tools/xenalyze: Remove argp_program_bug_address\n\nxenalyze sets argp_program_bug_address to my old Citrix address. This\nwas done before xenalyze was in the xen.git tree; and it's the only\nprogram in the tree which does so.\n\nNow that xenalyze is part of the normal Xen distribution, it should be\nobvious where to report bugs.\n\nSigned-off-by: George Dunlap \nAcked-by: Andrew Cooper \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"tools/xenalyze: Remove argp_program_bug_address"}},{"before":"3c7c9225ffa5605bf0603f9dd1666f3f786e2c44","after":"87a49d2ec6fe2881e4b0947ea3e0e0f041dc6be3","ref":"refs/heads/staging-4.17","pushedAt":"2024-06-26T12:28:37.000Z","pushType":"push","commitsCount":16,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"x86/irq: forward pending interrupts to new destination in fixup_irqs()\n\nfixup_irqs() is used to evacuate interrupts from to be offlined CPUs. Given\nthe CPU is to become offline, the normal migration logic used by Xen where the\nvector in the previous target(s) is left configured until the interrupt is\nreceived on the new destination is not suitable.\n\nInstead attempt to do as much as possible in order to prevent loosing\ninterrupts. If fixup_irqs() is called from the CPU to be offlined (as is\ncurrently the case for CPU hot unplug) attempt to forward pending vectors when\ninterrupts that target the current CPU are migrated to a different destination.\n\nAdditionally, for interrupts that have already been moved from the current CPU\nprior to the call to fixup_irqs() but that haven't been delivered to the new\ndestination (iow: interrupts with move_in_progress set and the current CPU set\nin ->arch.old_cpu_mask) also check whether the previous vector is pending and\nforward it to the new destination.\n\nThis allows us to remove the window with interrupts enabled at the bottom of\nfixup_irqs(). Such window wasn't safe anyway: references to the CPU to become\noffline are removed from interrupts masks, but the per-CPU vector_irq[] array\nis not updated to reflect those changes (as the CPU is going offline anyway).\n\nSigned-off-by: Roger Pau Monné \nReviewed-by: Jan Beulich \nmaster commit: e2bb28d621584fce15c907002ddc7c6772644b64\nmaster date: 2024-06-20 12:09:32 +0200","shortMessageHtmlLink":"x86/irq: forward pending interrupts to new destination in fixup_irqs()"}},{"before":"01f7a3c792241d348a4e454a30afdf6c0d6cd71c","after":"e95d30f9e5eed0c5d9dbf72d4cc3ae373152ab10","ref":"refs/heads/staging-4.18","pushedAt":"2024-06-26T12:02:37.000Z","pushType":"push","commitsCount":16,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"x86/irq: forward pending interrupts to new destination in fixup_irqs()\n\nfixup_irqs() is used to evacuate interrupts from to be offlined CPUs. Given\nthe CPU is to become offline, the normal migration logic used by Xen where the\nvector in the previous target(s) is left configured until the interrupt is\nreceived on the new destination is not suitable.\n\nInstead attempt to do as much as possible in order to prevent loosing\ninterrupts. If fixup_irqs() is called from the CPU to be offlined (as is\ncurrently the case for CPU hot unplug) attempt to forward pending vectors when\ninterrupts that target the current CPU are migrated to a different destination.\n\nAdditionally, for interrupts that have already been moved from the current CPU\nprior to the call to fixup_irqs() but that haven't been delivered to the new\ndestination (iow: interrupts with move_in_progress set and the current CPU set\nin ->arch.old_cpu_mask) also check whether the previous vector is pending and\nforward it to the new destination.\n\nThis allows us to remove the window with interrupts enabled at the bottom of\nfixup_irqs(). Such window wasn't safe anyway: references to the CPU to become\noffline are removed from interrupts masks, but the per-CPU vector_irq[] array\nis not updated to reflect those changes (as the CPU is going offline anyway).\n\nSigned-off-by: Roger Pau Monné \nReviewed-by: Jan Beulich \nmaster commit: e2bb28d621584fce15c907002ddc7c6772644b64\nmaster date: 2024-06-20 12:09:32 +0200","shortMessageHtmlLink":"x86/irq: forward pending interrupts to new destination in fixup_irqs()"}},{"before":"853f707cd9e2eb9410dbfbadbd5a01ac0252ef83","after":"4712e3b3769e6c03e0aaaa8179395f0fb7b141cc","ref":"refs/heads/staging","pushedAt":"2024-06-26T11:10:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"Config.mk: update MiniOS commit\n\nPull in the gcc14 build fix there.\n\nSigned-off-by: Jan Beulich \nReviewed-by: Juergen Gross \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"Config.mk: update MiniOS commit"}},{"before":"9e7c26ad8532c3efda174dee5ab8bdbeef1e4f6d","after":"11ea49a3fda5f0cbd8546ee8bdc5e9c55736c828","ref":"refs/heads/master","pushedAt":"2024-06-26T05:32:37.000Z","pushType":"push","commitsCount":18,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"gnttab: fix compat query-size handling\n\nThe odd DEFINE_XEN_GUEST_HANDLE(), inconsistent with all other similar\nconstructs, should have caught my attention. Turns out it was needed for\nthe build to succeed merely because the corresponding #ifndef had a\ntypo. That typo in turn broke compat mode guests, by having query-size\nrequests of theirs wire into the domain_crash() at the bottom of the\nswitch().\n\nFixes: 8c3bb4d8ce3f (\"xen/gnttab: Perform compat/native gnttab_query_size check\")\nSigned-off-by: Jan Beulich \nReviewed-by: Roger Pau Monné \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"gnttab: fix compat query-size handling"}},{"before":"11ea49a3fda5f0cbd8546ee8bdc5e9c55736c828","after":"853f707cd9e2eb9410dbfbadbd5a01ac0252ef83","ref":"refs/heads/smoke","pushedAt":"2024-06-26T03:48:36.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"automation/eclair_analysis: deviate and|or|xor|not for MISRA C Rule 21.2\n\nRule 21.2 reports identifiers reserved for the C and POSIX standard\nlibraries: or, and, not and xor are reserved identifiers because they\nconstitute alternate spellings for the corresponding operators (they are\ndefined as macros by iso646.h); however Xen doesn't use standard library\nheaders, so there is no risk of overlap.\n\nThis addresses violations arising from x86_emulate/x86_emulate.c, where\nlabel statements named as or, and and xor appear.\n\nNo functional change.\n\nSigned-off-by: Alessandro Zucchelli \nAcked-by: Stefano Stabellini \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"automation/eclair_analysis: deviate and|or|xor|not for MISRA C Rule 21.2"}},{"before":"11ea49a3fda5f0cbd8546ee8bdc5e9c55736c828","after":"853f707cd9e2eb9410dbfbadbd5a01ac0252ef83","ref":"refs/heads/staging","pushedAt":"2024-06-25T22:36:37.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"automation/eclair_analysis: deviate and|or|xor|not for MISRA C Rule 21.2\n\nRule 21.2 reports identifiers reserved for the C and POSIX standard\nlibraries: or, and, not and xor are reserved identifiers because they\nconstitute alternate spellings for the corresponding operators (they are\ndefined as macros by iso646.h); however Xen doesn't use standard library\nheaders, so there is no risk of overlap.\n\nThis addresses violations arising from x86_emulate/x86_emulate.c, where\nlabel statements named as or, and and xor appear.\n\nNo functional change.\n\nSigned-off-by: Alessandro Zucchelli \nAcked-by: Stefano Stabellini \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"automation/eclair_analysis: deviate and|or|xor|not for MISRA C Rule 21.2"}},{"before":"b14dae96c07ef27cc7f8107ddaa16989e9ab024b","after":"11ea49a3fda5f0cbd8546ee8bdc5e9c55736c828","ref":"refs/heads/smoke","pushedAt":"2024-06-25T14:22:37.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"gnttab: fix compat query-size handling\n\nThe odd DEFINE_XEN_GUEST_HANDLE(), inconsistent with all other similar\nconstructs, should have caught my attention. Turns out it was needed for\nthe build to succeed merely because the corresponding #ifndef had a\ntypo. That typo in turn broke compat mode guests, by having query-size\nrequests of theirs wire into the domain_crash() at the bottom of the\nswitch().\n\nFixes: 8c3bb4d8ce3f (\"xen/gnttab: Perform compat/native gnttab_query_size check\")\nSigned-off-by: Jan Beulich \nReviewed-by: Roger Pau Monné \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"gnttab: fix compat query-size handling"}},{"before":"c56f1ef577831ec70645ca5874d54f2e698c6761","after":"b14dae96c07ef27cc7f8107ddaa16989e9ab024b","ref":"refs/heads/smoke","pushedAt":"2024-06-25T10:28:37.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"x86/pagewalk: Address MISRA R8.3 violation in guest_walk_tables()\n\nCommit 4c5d78a10dc8 (\"x86/pagewalk: Re-implement the pagetable walker\")\nintentionally renamed guest_walk_tables()'s 'pfec' parameter to 'walk' because\nit's not a PageFault Error Code, despite the name of some of the constants\npassed in. Sadly the constants-cleanup I've been meaning to do since then\nstill hasn't come to pass.\n\nUpdate the declaration to match, to placate MISRA.\n\nFixes: 4c5d78a10dc8 (\"x86/pagewalk: Re-implement the pagetable walker\")\nSigned-off-by: Andrew Cooper \nReviewed-by: Stefano Stabellini \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"x86/pagewalk: Address MISRA R8.3 violation in guest_walk_tables()"}},{"before":"b14dae96c07ef27cc7f8107ddaa16989e9ab024b","after":"11ea49a3fda5f0cbd8546ee8bdc5e9c55736c828","ref":"refs/heads/staging","pushedAt":"2024-06-25T10:02:37.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"gnttab: fix compat query-size handling\n\nThe odd DEFINE_XEN_GUEST_HANDLE(), inconsistent with all other similar\nconstructs, should have caught my attention. Turns out it was needed for\nthe build to succeed merely because the corresponding #ifndef had a\ntypo. That typo in turn broke compat mode guests, by having query-size\nrequests of theirs wire into the domain_crash() at the bottom of the\nswitch().\n\nFixes: 8c3bb4d8ce3f (\"xen/gnttab: Perform compat/native gnttab_query_size check\")\nSigned-off-by: Jan Beulich \nReviewed-by: Roger Pau Monné \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"gnttab: fix compat query-size handling"}},{"before":"c56f1ef577831ec70645ca5874d54f2e698c6761","after":"b14dae96c07ef27cc7f8107ddaa16989e9ab024b","ref":"refs/heads/staging","pushedAt":"2024-06-25T00:56:37.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"x86/pagewalk: Address MISRA R8.3 violation in guest_walk_tables()\n\nCommit 4c5d78a10dc8 (\"x86/pagewalk: Re-implement the pagetable walker\")\nintentionally renamed guest_walk_tables()'s 'pfec' parameter to 'walk' because\nit's not a PageFault Error Code, despite the name of some of the constants\npassed in. Sadly the constants-cleanup I've been meaning to do since then\nstill hasn't come to pass.\n\nUpdate the declaration to match, to placate MISRA.\n\nFixes: 4c5d78a10dc8 (\"x86/pagewalk: Re-implement the pagetable walker\")\nSigned-off-by: Andrew Cooper \nReviewed-by: Stefano Stabellini \nRelease-Acked-by: Oleksii Kurochko ","shortMessageHtmlLink":"x86/pagewalk: Address MISRA R8.3 violation in guest_walk_tables()"}},{"before":"908407bf2b29a38d6879fc8c57dad14473ef67f8","after":"c56f1ef577831ec70645ca5874d54f2e698c6761","ref":"refs/heads/smoke","pushedAt":"2024-06-24T23:12:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"hubot","name":"Hubot","path":"/hubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/480938?s=80&v=4"},"commit":{"message":"xen/arm: static-shmem: request host address to be specified for 1:1 domains\n\nAs a follow up to commit cb1ddafdc573 (\"xen/arm/static-shmem: Static-shmem\nshould be direct-mapped for direct-mapped domains\") add a check to\nrequest that both host and guest physical address must be supplied for\ndirect mapped domains. Otherwise return an error to prevent unwanted\nbehavior.\n\nSigned-off-by: Michal Orzel \nFixes: 988f1c7e1f40 (\"xen/arm: static-shmem: fix \"gbase/pbase used uninitialized\" build failure\")\nReviewed-by: Julien Grall \nRelease-Acked-By: Oleksii Kurochko ","shortMessageHtmlLink":"xen/arm: static-shmem: request host address to be specified for 1:1 d…"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEcmk1ywA","startCursor":null,"endCursor":null}},"title":"Activity · xen-project/xen"}