[Qemu-devel] [Bug 1810545] Re: [alpha] Strange exception address reported

2019-04-23 Thread Thomas Huth
** Changed in: qemu Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1810545 Title: [alpha] Strange exception address reported Status in QEMU: Fix Relea

[Qemu-devel] [Bug 1810545] Re: [alpha] Strange exception address reported

2019-01-08 Thread Stefan Ring
Works, thanks! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1810545 Title: [alpha] Strange exception address reported Status in QEMU: Fix Committed Bug description: For some reason the SIGIL

[Qemu-devel] [Bug 1810545] Re: [alpha] Strange exception address reported

2019-01-08 Thread Peter Maydell
commit ac89de40ef5d4eb1704aa now in QEMU git master updates the palcode guest ROM blob to a version which includes the fix for this bug. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed

Re: [Qemu-devel] [Bug 1810545] Re: [alpha] Strange exception address reported

2019-01-07 Thread Richard Henderson
On 1/8/19 5:00 AM, Peter Maydell wrote: > On Mon, 7 Jan 2019 at 18:10, Peter Maydell wrote: > (re: https://bugs.launchpad.net/bugs/1810545) > >> The problem seems to be that the PC we report for an OPCDEC >> is first selected by gen_invalid()/gen_excp() in >> target/alpha/translate.c, which uses

Re: [Qemu-devel] [Bug 1810545] Re: [alpha] Strange exception address reported

2019-01-07 Thread Peter Maydell
On Mon, 7 Jan 2019 at 18:10, Peter Maydell wrote: (re: https://bugs.launchpad.net/bugs/1810545) > The problem seems to be that the PC we report for an OPCDEC > is first selected by gen_invalid()/gen_excp() in > target/alpha/translate.c, which uses pc_next (ie the insn's > address plus 4). But tha

[Qemu-devel] [Bug 1810545] Re: [alpha] Strange exception address reported

2019-01-07 Thread Peter Maydell
The problem seems to be that the PC we report for an OPCDEC is first selected by gen_invalid()/gen-excp() in target/alpha/translate.c, which uses pc_next (ie the insn's address plus 4). But that is then handed through to our custom PALcode (https://git.qemu.org/?p=qemu-palcode.git;a=blob;f=pal.

[Qemu-devel] [Bug 1810545] Re: [alpha] Strange exception address reported

2019-01-04 Thread Peter Maydell
Hmm, qemu-system-alpha ? The guest kernel should be doing the same thing it would on real hardware -- I guess we're getting the value of the exception address wrong when we deliver the exception to it. -- You received this bug notification because you are a member of qemu- devel-ml, which is subs