Re: [PATCH v12 1/3] xen/riscv: enable GENERIC_BUG_FRAME

2024-08-06 Thread Jan Beulich
On 06.08.2024 12:11, oleksii.kuroc...@gmail.com wrote: > On Mon, 2024-08-05 at 17:41 +0200, Jan Beulich wrote: >> On 02.08.2024 15:54, Oleksii Kurochko wrote: >>> Enable GENERIC_BUG_FRAME to support BUG(), WARN(), ASSERT, >>> and run_in_exception_handler(). >>> >>> The 0x opcode is used for BUG

Re: [PATCH v12 1/3] xen/riscv: enable GENERIC_BUG_FRAME

2024-08-06 Thread oleksii . kurochko
On Mon, 2024-08-05 at 17:41 +0200, Jan Beulich wrote: > On 02.08.2024 15:54, Oleksii Kurochko wrote: > > Enable GENERIC_BUG_FRAME to support BUG(), WARN(), ASSERT, > > and run_in_exception_handler(). > > > > The 0x opcode is used for BUG_INSTR, which, when macros from > > are used, triggers a

Re: [PATCH v12 1/3] xen/riscv: enable GENERIC_BUG_FRAME

2024-08-05 Thread Jan Beulich
On 02.08.2024 15:54, Oleksii Kurochko wrote: > Enable GENERIC_BUG_FRAME to support BUG(), WARN(), ASSERT, > and run_in_exception_handler(). > > The 0x opcode is used for BUG_INSTR, which, when macros from > are used, triggers an exception with the > ILLEGAL_INSTRUCTION cause. > This opcode is

[PATCH v12 1/3] xen/riscv: enable GENERIC_BUG_FRAME

2024-08-02 Thread Oleksii Kurochko
Enable GENERIC_BUG_FRAME to support BUG(), WARN(), ASSERT, and run_in_exception_handler(). The 0x opcode is used for BUG_INSTR, which, when macros from are used, triggers an exception with the ILLEGAL_INSTRUCTION cause. This opcode is encoded as a 2-byte instruction and is invalid if CONFIG_R