From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: [PATCH v2] x86/emul: Split exception handling out of invoke_stub()
Date: Wed, 31 Jan 2018 12:50:59 +0000 [thread overview]
Message-ID: <1517403059-21284-1-git-send-email-andrew.cooper3@citrix.com> (raw)
For a release build, bloat-o-meter reports:
add/remove: 0/0 grow/shrink: 0/1 up/down: 0/-5111 (-5111)
function old new delta
x86_emulate 126458 121347 -5111
or in other words, a 4% redunction in code size from this change alone.
The use of __LINE__ is a concern with livepatching, but any livepatch touching
this file is overwhemlingly likely to alter x86_emulate() anyway.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
---
CC: Jan Beulich <JBeulich@suse.com>
v2:
* Retain __LINE__. It can't be embedded in union stub_exception_token as the
full token gets written by the exception hanlder.
---
xen/arch/x86/x86_emulate/x86_emulate.c | 37 +++++++++++++++++++++-------------
1 file changed, 23 insertions(+), 14 deletions(-)
diff --git a/xen/arch/x86/x86_emulate/x86_emulate.c b/xen/arch/x86/x86_emulate/x86_emulate.c
index 4cc51ea..c9221c8 100644
--- a/xen/arch/x86/x86_emulate/x86_emulate.c
+++ b/xen/arch/x86/x86_emulate/x86_emulate.c
@@ -866,7 +866,8 @@ static inline int mkec(uint8_t e, int32_t ec, ...)
#ifdef __XEN__
# define invoke_stub(pre, post, constraints...) do { \
- union stub_exception_token res_ = { .raw = ~0 }; \
+ stub_exn_info = (union stub_exception_token) { .raw = ~0 }; \
+ stub_exn_line = __LINE__; /* Utility outweighs livepatching cost */ \
asm volatile ( pre "\n\tINDIRECT_CALL %[stub]\n\t" post "\n" \
".Lret%=:\n\t" \
".pushsection .fixup,\"ax\"\n" \
@@ -875,21 +876,11 @@ static inline int mkec(uint8_t e, int32_t ec, ...)
"jmp .Lret%=\n\t" \
".popsection\n\t" \
_ASM_EXTABLE(.Lret%=, .Lfix%=) \
- : [exn] "+g" (res_), constraints, \
+ : [exn] "+g" (stub_exn_info), constraints, \
[stub] "r" (stub.func), \
"m" (*(uint8_t(*)[MAX_INST_LEN + 1])stub.ptr) ); \
- if ( unlikely(~res_.raw) ) \
- { \
- gprintk(XENLOG_WARNING, \
- "exception %u (ec=%04x) in emulation stub (line %u)\n", \
- res_.fields.trapnr, res_.fields.ec, __LINE__); \
- gprintk(XENLOG_INFO, "stub: %"__stringify(MAX_INST_LEN)"ph\n", \
- stub.func); \
- generate_exception_if(res_.fields.trapnr == EXC_UD, EXC_UD); \
- domain_crash(current->domain); \
- rc = X86EMUL_UNHANDLEABLE; \
- goto done; \
- } \
+ if ( unlikely(~stub_exn_info.raw) ) \
+ goto emulation_stub_failure; \
} while (0)
#else
# define invoke_stub(pre, post, constraints...) \
@@ -3017,6 +3008,10 @@ x86_emulate(
struct fpu_insn_ctxt fic = { .type = X86EMUL_FPU_none, .exn_raised = -1 };
struct x86_emulate_stub stub = {};
DECLARE_ALIGNED(mmval_t, mmval);
+#ifdef __XEN__
+ union stub_exception_token stub_exn_info;
+ unsigned int stub_exn_line;
+#endif
ASSERT(ops->read);
@@ -8023,6 +8018,20 @@ x86_emulate(
put_stub(stub);
return rc;
#undef state
+
+#ifdef __XEN__
+ emulation_stub_failure:
+ gprintk(XENLOG_WARNING,
+ "exception %u (ec=%04x) in emulation stub (line %u)\n",
+ stub_exn_info.fields.trapnr, stub_exn_info.fields.ec,
+ stub_exn_line);
+ gprintk(XENLOG_INFO, " stub: %"__stringify(MAX_INST_LEN)"ph\n",
+ stub.func);
+ generate_exception_if(stub_exn_info.fields.trapnr == EXC_UD, EXC_UD);
+ domain_crash(current->domain);
+ rc = X86EMUL_UNHANDLEABLE;
+ goto done;
+#endif
}
#undef op_bytes
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-01-31 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 12:50 Andrew Cooper [this message]
2018-02-01 9:20 ` [PATCH v2] x86/emul: Split exception handling out of invoke_stub() Jan Beulich
2018-02-01 9:41 ` Andrew Cooper
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=1517403059-21284-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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).