From: Andrii Anisov <andrii.anisov@gmail.com> To: Julien Grall <julien.grall@arm.com> Cc: Juergen Gross <jgross@suse.com>, xen-devel <xen-devel@lists.xenproject.org>, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Stefano Stabellini <sstabellini@kernel.org> Subject: Re: [PATCH v2 0/2] Introduce runstate area registration with phys address Date: Wed, 8 May 2019 19:01:28 +0300 [thread overview] Message-ID: <b7cb8324-45ae-8840-b73e-c7dd508e954e@gmail.com> (raw) In-Reply-To: <98200ea9-c21e-9d58-498d-468764209972@arm.com> Hello Julien, On 08.05.19 17:31, Julien Grall wrote: > I haven't seen them with nokpti platform so far. I am curious to know what is your configuration here. XEN 4.12 with our patches. Thin Dom0 is a generic armv8 Linux, LK 4.14.75 with patches from Renesas and us. DomD is LK 4.14.75 with HW assigned and drivers. LK configs you can find on my google drive [1]. Those faults fire only for DomD (on its start). > vcpu_show_execution_state(current) should do the job here. Here it is: (XEN) d1v2 par 0x809 (XEN) d1v2: Failed to walk page-table va 0xffff80002ff66357 (XEN) *** Dumping Dom1 vcpu#2 state: *** (XEN) ----[ Xen-4.12.0 arm64 debug=n Not tainted ]---- (XEN) CPU: 2 (XEN) PC: 0000ffffbd28dc88 (XEN) LR: 0000ffffbd28e674 (XEN) SP_EL0: 0000ffffe9890410 (XEN) SP_EL1: ffff00000803c000 (XEN) CPSR: 40000000 MODE:64-bit EL0t (Guest User) (XEN) X0: 0000000000000000 X1: 0000ffffe98907bc X2: 0000ffffe9890430 (XEN) X3: 0000000000000000 X4: 0000000000000000 X5: 0000000000000000 (XEN) X6: 0000000000000001 X7: 0000ffffe98907b8 X8: 0101010101010101 (XEN) X9: 0000000000000000 X10: 0000ffffe9890570 X11: 0000000000000020 (XEN) X12: 0000000000000000 X13: 0000000000000000 X14: 0000000000000015 (XEN) X15: 000000000000000a X16: 0000ffffbd6502c8 X17: 0000ffffbd28e660 (XEN) X18: 0000ffffe98902cf X19: 0000ffffe98907b8 X20: 0000ffffe98907b8 (XEN) X21: 0000ffffbd653000 X22: 0000ffffe98906f8 X23: 000000000000001e (XEN) X24: 0000ffffe98906a8 X25: 0000ffffbd584000 X26: 0000aaaac8736f68 (XEN) X27: 0000ffffbd584978 X28: 0000000000000002 FP: 0000ffffe9890410 (XEN) (XEN) ELR_EL1: 0000ffffbd2b4698 (XEN) ESR_EL1: 56000000 (XEN) FAR_EL1: 0000ffffbd525014 (XEN) (XEN) SCTLR_EL1: 34d5d91d (XEN) TCR_EL1: 34b5503510 (XEN) TTBR0_EL1: 000000006c056000 (XEN) TTBR1_EL1: 00030000412d8000 (XEN) (XEN) VTCR_EL2: 80023558 (XEN) VTTBR_EL2: 000200073fed6000 (XEN) (XEN) SCTLR_EL2: 30cd183d (XEN) HCR_EL2: 000000008078663f (XEN) TTBR0_EL2: 0000000078184000 (XEN) (XEN) ESR_EL2: 5a000ea1 (XEN) HPFAR_EL2: 0000000000030010 (XEN) FAR_EL2: ffff000008005f00 (XEN) (XEN) No stack trace for guest user-mode BTW, we have another public holiday tomorrow, so I'll get back to you on Friday. [1] https://drive.google.com/drive/folders/1SX0FhAOKrkFdbNELFuBUt7fmLZKb8XmK?usp=sharing -- Sincerely, Andrii Anisov. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andrii Anisov <andrii.anisov@gmail.com> To: Julien Grall <julien.grall@arm.com> Cc: Juergen Gross <jgross@suse.com>, xen-devel <xen-devel@lists.xenproject.org>, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Stefano Stabellini <sstabellini@kernel.org> Subject: Re: [Xen-devel] [PATCH v2 0/2] Introduce runstate area registration with phys address Date: Wed, 8 May 2019 19:01:28 +0300 [thread overview] Message-ID: <b7cb8324-45ae-8840-b73e-c7dd508e954e@gmail.com> (raw) Message-ID: <20190508160128.lMoaCnGY5vlMrK7FUXVODeZxtd30VOWHRPRNpFInXDw@z> (raw) In-Reply-To: <98200ea9-c21e-9d58-498d-468764209972@arm.com> Hello Julien, On 08.05.19 17:31, Julien Grall wrote: > I haven't seen them with nokpti platform so far. I am curious to know what is your configuration here. XEN 4.12 with our patches. Thin Dom0 is a generic armv8 Linux, LK 4.14.75 with patches from Renesas and us. DomD is LK 4.14.75 with HW assigned and drivers. LK configs you can find on my google drive [1]. Those faults fire only for DomD (on its start). > vcpu_show_execution_state(current) should do the job here. Here it is: (XEN) d1v2 par 0x809 (XEN) d1v2: Failed to walk page-table va 0xffff80002ff66357 (XEN) *** Dumping Dom1 vcpu#2 state: *** (XEN) ----[ Xen-4.12.0 arm64 debug=n Not tainted ]---- (XEN) CPU: 2 (XEN) PC: 0000ffffbd28dc88 (XEN) LR: 0000ffffbd28e674 (XEN) SP_EL0: 0000ffffe9890410 (XEN) SP_EL1: ffff00000803c000 (XEN) CPSR: 40000000 MODE:64-bit EL0t (Guest User) (XEN) X0: 0000000000000000 X1: 0000ffffe98907bc X2: 0000ffffe9890430 (XEN) X3: 0000000000000000 X4: 0000000000000000 X5: 0000000000000000 (XEN) X6: 0000000000000001 X7: 0000ffffe98907b8 X8: 0101010101010101 (XEN) X9: 0000000000000000 X10: 0000ffffe9890570 X11: 0000000000000020 (XEN) X12: 0000000000000000 X13: 0000000000000000 X14: 0000000000000015 (XEN) X15: 000000000000000a X16: 0000ffffbd6502c8 X17: 0000ffffbd28e660 (XEN) X18: 0000ffffe98902cf X19: 0000ffffe98907b8 X20: 0000ffffe98907b8 (XEN) X21: 0000ffffbd653000 X22: 0000ffffe98906f8 X23: 000000000000001e (XEN) X24: 0000ffffe98906a8 X25: 0000ffffbd584000 X26: 0000aaaac8736f68 (XEN) X27: 0000ffffbd584978 X28: 0000000000000002 FP: 0000ffffe9890410 (XEN) (XEN) ELR_EL1: 0000ffffbd2b4698 (XEN) ESR_EL1: 56000000 (XEN) FAR_EL1: 0000ffffbd525014 (XEN) (XEN) SCTLR_EL1: 34d5d91d (XEN) TCR_EL1: 34b5503510 (XEN) TTBR0_EL1: 000000006c056000 (XEN) TTBR1_EL1: 00030000412d8000 (XEN) (XEN) VTCR_EL2: 80023558 (XEN) VTTBR_EL2: 000200073fed6000 (XEN) (XEN) SCTLR_EL2: 30cd183d (XEN) HCR_EL2: 000000008078663f (XEN) TTBR0_EL2: 0000000078184000 (XEN) (XEN) ESR_EL2: 5a000ea1 (XEN) HPFAR_EL2: 0000000000030010 (XEN) FAR_EL2: ffff000008005f00 (XEN) (XEN) No stack trace for guest user-mode BTW, we have another public holiday tomorrow, so I'll get back to you on Friday. [1] https://drive.google.com/drive/folders/1SX0FhAOKrkFdbNELFuBUt7fmLZKb8XmK?usp=sharing -- Sincerely, Andrii Anisov. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-08 16:01 UTC|newest] Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-23 8:10 [PATCH v2 0/2] Introduce runstate area registration with phys address Andrii Anisov 2019-04-23 8:10 ` [PATCH v2 1/2] xen: introduce VCPUOP_register_runstate_phys_memory_area hypercall Andrii Anisov 2019-04-23 8:10 ` [Xen-devel] " Andrii Anisov 2019-05-08 10:10 ` George Dunlap 2019-05-08 10:10 ` [Xen-devel] " George Dunlap 2019-04-23 8:10 ` [PATCH v2 2/2] xen: implement VCPUOP_register_runstate_phys_memory_area Andrii Anisov 2019-04-23 8:10 ` [Xen-devel] " Andrii Anisov 2019-05-08 15:40 ` Julien Grall 2019-05-08 15:40 ` [Xen-devel] " Julien Grall 2019-05-09 9:27 ` Jan Beulich 2019-05-09 9:27 ` [Xen-devel] " Jan Beulich 2019-05-14 9:35 ` Julien Grall 2019-05-14 9:35 ` [Xen-devel] " Julien Grall 2019-05-14 9:48 ` Jan Beulich 2019-05-14 9:48 ` [Xen-devel] " Jan Beulich 2019-05-14 11:23 ` Julien Grall 2019-05-14 11:23 ` [Xen-devel] " Julien Grall 2019-05-14 11:29 ` Jan Beulich 2019-05-14 11:29 ` [Xen-devel] " Jan Beulich 2019-05-13 12:30 ` Andrii Anisov 2019-05-13 12:30 ` [Xen-devel] " Andrii Anisov 2019-05-14 9:58 ` Julien Grall 2019-05-14 9:58 ` [Xen-devel] " Julien Grall 2019-05-14 10:08 ` Andrii Anisov 2019-05-14 10:08 ` [Xen-devel] " Andrii Anisov 2019-05-14 11:24 ` Julien Grall 2019-05-14 11:24 ` [Xen-devel] " Julien Grall 2019-05-14 11:45 ` Andrii Anisov 2019-05-14 11:45 ` [Xen-devel] " Andrii Anisov 2019-05-14 12:02 ` Jan Beulich 2019-05-14 12:02 ` [Xen-devel] " Jan Beulich 2019-05-14 13:05 ` Andrii Anisov 2019-05-14 13:05 ` [Xen-devel] " Andrii Anisov 2019-05-14 13:49 ` Julien Grall 2019-05-14 13:49 ` [Xen-devel] " Julien Grall 2019-05-15 9:04 ` Andrii Anisov 2019-05-15 9:04 ` [Xen-devel] " Andrii Anisov 2019-05-15 10:31 ` Julien Grall 2019-05-15 10:31 ` [Xen-devel] " Julien Grall 2019-05-14 13:49 ` Jan Beulich 2019-05-14 13:49 ` [Xen-devel] " Jan Beulich 2019-05-15 8:44 ` Andrii Anisov 2019-05-15 8:44 ` [Xen-devel] " Andrii Anisov 2019-05-15 11:59 ` Jan Beulich 2019-05-15 11:59 ` [Xen-devel] " Jan Beulich 2019-05-16 12:09 ` Jan Beulich 2019-05-16 12:09 ` [Xen-devel] " Jan Beulich 2019-05-16 13:30 ` Andrii Anisov 2019-05-16 13:30 ` [Xen-devel] " Andrii Anisov 2019-05-16 13:30 ` Andrii Anisov 2019-05-16 13:30 ` [Xen-devel] " Andrii Anisov 2019-05-16 13:48 ` Julien Grall 2019-05-16 13:48 ` [Xen-devel] " Julien Grall 2019-05-16 14:25 ` Andrii Anisov 2019-05-16 14:25 ` [Xen-devel] " Andrii Anisov 2019-05-16 14:28 ` Julien Grall 2019-05-16 14:28 ` [Xen-devel] " Julien Grall 2019-05-16 14:29 ` Andrii Anisov 2019-05-16 14:29 ` [Xen-devel] " Andrii Anisov [not found] ` <fa126315-31af-854e-817a-8640b431c82b@arm.com> [not found] ` <CAC1WxdiMzAq5hRC-mhRQuFDs7z_Hj5w7VAy52ec87SJQOGmp3w@mail.gmail.com> [not found] ` <a28f95a1-d9da-2caf-f4b4-013100176b02@arm.com> [not found] ` <090ce8cc-f329-fe54-4894-b7f12e3cd5a6@gmail.com> 2019-05-08 13:39 ` [PATCH v2 0/2] Introduce runstate area registration with phys address Julien Grall 2019-05-08 13:39 ` [Xen-devel] " Julien Grall 2019-05-08 13:54 ` Andrii Anisov 2019-05-08 13:54 ` [Xen-devel] " Andrii Anisov 2019-05-08 14:31 ` Julien Grall 2019-05-08 14:31 ` [Xen-devel] " Julien Grall 2019-05-08 16:01 ` Andrii Anisov [this message] 2019-05-08 16:01 ` Andrii Anisov 2019-05-13 10:50 ` Julien Grall 2019-05-13 10:50 ` [Xen-devel] " Julien Grall 2019-05-13 14:34 ` Andrii Anisov 2019-05-13 14:34 ` [Xen-devel] " Andrii Anisov 2019-05-08 13:59 ` Julien Grall 2019-05-13 10:15 ` Andrii Anisov 2019-05-13 11:16 ` Julien Grall 2019-05-13 14:14 ` Andrii Anisov 2019-05-13 14:34 ` Julien Grall 2019-05-13 15:29 ` Andrii Anisov 2019-05-13 15:31 ` Julien Grall 2019-05-13 15:38 ` Andrii Anisov 2019-05-13 15:40 ` Julien Grall 2019-05-13 15:42 ` Andrii Anisov 2019-05-13 15:45 ` Julien Grall 2019-05-13 16:05 ` Andrii Anisov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=b7cb8324-45ae-8840-b73e-c7dd508e954e@gmail.com \ --to=andrii.anisov@gmail.com \ --cc=boris.ostrovsky@oracle.com \ --cc=jgross@suse.com \ --cc=julien.grall@arm.com \ --cc=sstabellini@kernel.org \ --cc=xen-devel@lists.xenproject.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).