From: Wei Liu <wl@xen.org>
To: Xen Development List <xen-devel@lists.xenproject.org>
Cc: "Wei Liu" <liuwe@microsoft.com>, "Wei Liu" <wl@xen.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Michael Kelley" <mikelley@microsoft.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH for-next v3 4/9] x86: include xen/lib.h in guest/hypercall.h
Date: Mon, 21 Oct 2019 16:57:13 +0100 [thread overview]
Message-ID: <20191021155718.28653-5-liuwe@microsoft.com> (raw)
In-Reply-To: <20191021155718.28653-1-liuwe@microsoft.com>
We need ASSERT_UNREACHABLE.
Signed-off-by: Wei Liu <liuwe@microsoft.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
---
xen/include/asm-x86/guest/hypercall.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen/include/asm-x86/guest/hypercall.h b/xen/include/asm-x86/guest/hypercall.h
index c9deca6ffc..d0d2f5022d 100644
--- a/xen/include/asm-x86/guest/hypercall.h
+++ b/xen/include/asm-x86/guest/hypercall.h
@@ -182,6 +182,8 @@ static inline long xen_hypercall_set_evtchn_upcall_vector(
#else /* CONFIG_XEN_GUEST */
+#include <xen/lib.h>
+
#include <public/sched.h>
static inline void xen_hypercall_console_write(
--
2.20.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-21 15:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 15:57 [Xen-devel] [PATCH for-next v3 0/9] Port Xen to Hyper-V Wei Liu
2019-10-21 15:57 ` [Xen-devel] [PATCH for-next v3 1/9] x86: introduce CONFIG_GUEST and move code Wei Liu
2019-10-23 7:55 ` Paul Durrant
2019-10-23 10:49 ` Wei Liu
2019-11-15 13:34 ` Jan Beulich
2019-10-21 15:57 ` [Xen-devel] [PATCH for-next v3 2/9] x86: include asm_defns.h directly in hypercall.h Wei Liu
2019-11-15 13:36 ` Jan Beulich
2019-10-21 15:57 ` [Xen-devel] [PATCH for-next v3 3/9] x86: drop hypervisor_cpuid_base Wei Liu
2019-11-15 13:39 ` Jan Beulich
2019-10-21 15:57 ` Wei Liu [this message]
2019-11-15 13:40 ` [Xen-devel] [PATCH for-next v3 4/9] x86: include xen/lib.h in guest/hypercall.h Jan Beulich
2019-10-21 15:57 ` [Xen-devel] [PATCH for-next v3 5/9] x86: introduce hypervisor framework Wei Liu
2019-10-23 8:19 ` Paul Durrant
2019-11-15 13:48 ` Jan Beulich
2019-11-21 16:27 ` Wei Liu
2019-10-21 15:57 ` [Xen-devel] [PATCH for-next v3 6/9] x86: rename hypervisor_{alloc, free}_unused_page Wei Liu
2019-11-15 13:49 ` Jan Beulich
2019-11-21 16:27 ` Wei Liu
2019-10-21 15:57 ` [Xen-devel] [PATCH for-next v3 7/9] x86: switch xen implementation to use hypervisor framework Wei Liu
2019-10-23 9:02 ` Paul Durrant
2019-11-15 13:56 ` Jan Beulich
2019-10-21 15:57 ` [Xen-devel] [PATCH for-next v3 8/9] x86: be more verbose when running on a hypervisor Wei Liu
2019-10-23 9:03 ` Paul Durrant
2019-11-15 13:59 ` Jan Beulich
2019-10-21 15:57 ` [Xen-devel] [PATCH for-next v3 9/9] x86: introduce CONFIG_HYPERV and detection code Wei Liu
2019-10-23 9:07 ` Paul Durrant
2019-10-23 10:50 ` Wei Liu
2019-11-15 14:07 ` Jan Beulich
2019-11-21 16:27 ` Wei Liu
2019-11-21 16:59 ` Jan Beulich
2019-11-21 17:02 ` Wei Liu
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=20191021155718.28653-5-liuwe@microsoft.com \
--to=wl@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=liuwe@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=roger.pau@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.