From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xenproject.org
Cc: Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v3 4/7] x86: rearrange x86_64/entry.S
Date: Mon, 5 Nov 2018 14:20:42 +0000 [thread overview]
Message-ID: <58d7cd8f-0632-cc71-57eb-04b7bf4f96f7@citrix.com> (raw)
In-Reply-To: <805e6a102f30fa54f1ba1730db13bb1d3972dd5e.1541174103.git-series.wei.liu2@citrix.com>
On 02/11/18 15:55, Wei Liu wrote:
> @@ -553,8 +523,43 @@ ENTRY(dom_crash_sync_extable)
> jmp asm_domain_crash_synchronous /* Does not return */
> .popsection
>
> +/* --- CODE BELOW THIS LINE (MOSTLY) NOT GUEST RELATED --- */
> +
> + .text
> +
> + ALIGN
No need for an ALIGN here. There is one inside ENTRY().
Otherwise, Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> +/* No special register assumptions. */
> +ENTRY(ret_from_intr)
> + GET_CURRENT(bx)
> + testb $3, UREGS_cs(%rsp)
> + jz restore_all_xen
> + movq VCPU_domain(%rbx), %rax
> + cmpb $0, DOMAIN_is_32bit_pv(%rax)
> + je test_all_events
> + jmp compat_test_all_events
> +
> .section .text.entry, "ax", @progbits
>
> + ALIGN
> +/* No special register assumptions. */
> +restore_all_xen:
> + /*
> + * Check whether we need to switch to the per-CPU page tables, in
> + * case we return to late PV exit code (from an NMI or #MC).
> + */
> + GET_STACK_END(bx)
> + cmpb $0, STACK_CPUINFO_FIELD(use_pv_cr3)(%rbx)
> +UNLIKELY_START(ne, exit_cr3)
> + mov STACK_CPUINFO_FIELD(pv_cr3)(%rbx), %rax
> + mov %rax, %cr3
> +UNLIKELY_END(exit_cr3)
> +
> + /* WARNING! `ret`, `call *`, `jmp *` not safe beyond this point. */
> + SPEC_CTRL_EXIT_TO_XEN_IST /* Req: %rbx=end, Clob: acd */
> +
> + RESTORE_ALL adj=8
> + iretq
> +
> ENTRY(common_interrupt)
> SAVE_ALL CLAC
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-11-05 14:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 15:55 [PATCH v3 0/7] Make CONFIG_PV work on x86 Wei Liu
2018-11-02 15:55 ` [PATCH v3 1/7] x86: make traps.c build with !CONFIG_PV Wei Liu
2018-11-05 14:07 ` Andrew Cooper
2018-11-02 15:55 ` [PATCH v3 2/7] x86/domctl: rework XEN_DOMCTL_{set, get}_address_size Wei Liu
2018-11-05 14:08 ` Andrew Cooper
2018-11-02 15:55 ` [PATCH v3 3/7] x86: make PV hypercall entry points work with !CONFIG_PV Wei Liu
2018-11-05 14:13 ` Andrew Cooper
2018-11-05 15:04 ` Jan Beulich
2018-11-05 15:48 ` Wei Liu
2018-11-05 15:49 ` Andrew Cooper
2018-11-05 15:51 ` Wei Liu
2018-11-05 16:11 ` Jan Beulich
2018-11-08 15:33 ` Wei Liu
2018-11-08 15:36 ` Andrew Cooper
2018-11-08 15:49 ` Jan Beulich
2018-11-08 16:09 ` Wei Liu
2018-11-08 16:22 ` Jan Beulich
2018-11-08 16:42 ` Wei Liu
2018-11-08 15:39 ` Jan Beulich
2018-11-08 15:49 ` Wei Liu
2018-11-02 15:55 ` [PATCH v3 4/7] x86: rearrange x86_64/entry.S Wei Liu
2018-11-05 14:20 ` Andrew Cooper [this message]
2018-11-02 15:55 ` [PATCH v3 5/7] x86: make entry point code build when !CONFIG_PV Wei Liu
2018-11-05 14:33 ` Andrew Cooper
2018-11-05 17:08 ` Wei Liu
2018-11-05 17:10 ` Andrew Cooper
2018-11-02 15:55 ` [PATCH v3 6/7] x86: expose CONFIG_PV Wei Liu
2018-11-02 15:55 ` [PATCH v3 7/7] x86: update help string for CONFIG_HVM Wei Liu
2018-11-05 15:20 ` Jan Beulich
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=58d7cd8f-0632-cc71-57eb-04b7bf4f96f7@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=wei.liu2@citrix.com \
--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: link
Be 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).