From: vsntk18@gmail.com
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, seanjc@google.com, jroedel@suse.de,
papaluri@amd.com, andrew.jones@linux.dev,
Vasant Karasulli <vkarasulli@suse.de>,
Varad Gautam <varad.gautam@suse.com>
Subject: [kvm-unit-tests PATCH v7 03/11] lib: Define unlikely()/likely() macros in compiler.h
Date: Fri, 19 Apr 2024 18:16:15 +0200 [thread overview]
Message-ID: <20240419161623.45842-4-vsntk18@gmail.com> (raw)
In-Reply-To: <20240419161623.45842-1-vsntk18@gmail.com>
From: Vasant Karasulli <vkarasulli@suse.de>
So that they can be shared across testcases and lib/.
Linux's x86 instruction decoder refrences them.
Signed-off-by: Varad Gautam <varad.gautam@suse.com>
Signed-off-by: Vasant Karasulli <vkarasulli@suse.de>
---
lib/linux/compiler.h | 3 +++
x86/kvmclock.c | 4 ----
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/lib/linux/compiler.h b/lib/linux/compiler.h
index bf3313bd..9f4ef162 100644
--- a/lib/linux/compiler.h
+++ b/lib/linux/compiler.h
@@ -121,5 +121,8 @@ static __always_inline void __write_once_size(volatile void *p, void *res, int s
__u.__val; \
})
+#define unlikely(x) __builtin_expect(!!(x), 0)
+#define likely(x) __builtin_expect(!!(x), 1)
+
#endif /* !__ASSEMBLY__ */
#endif /* !__LINUX_COMPILER_H */
diff --git a/x86/kvmclock.c b/x86/kvmclock.c
index f9f21032..487c12af 100644
--- a/x86/kvmclock.c
+++ b/x86/kvmclock.c
@@ -5,10 +5,6 @@
#include "kvmclock.h"
#include "asm/barrier.h"
-#define unlikely(x) __builtin_expect(!!(x), 0)
-#define likely(x) __builtin_expect(!!(x), 1)
-
-
struct pvclock_vcpu_time_info __attribute__((aligned(4))) hv_clock[MAX_CPU];
struct pvclock_wall_clock wall_clock;
static unsigned char valid_flags = 0;
--
2.34.1
next prev parent reply other threads:[~2024-04-19 16:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 16:16 [kvm-unit-tests PATCH v7 00/11] Add #VC exception handling for AMD SEV-ES vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 01/11] x86: AMD SEV-ES: Setup #VC exception handler " vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 02/11] x86: Move svm.h to lib/x86/ vsntk18
2024-06-05 16:05 ` Sean Christopherson
2024-06-06 18:57 ` Vasant Karasulli
2024-04-19 16:16 ` vsntk18 [this message]
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 04/11] lib: x86: Import insn decoder from Linux vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 05/11] x86: AMD SEV-ES: Pull related GHCB definitions and helpers " vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 06/11] x86: AMD SEV-ES: Prepare for #VC processing vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 07/11] lib/x86: Move xsave helpers to lib/ vsntk18
2024-06-05 16:04 ` Sean Christopherson
2024-06-06 18:58 ` Vasant Karasulli
2024-06-06 23:49 ` Sean Christopherson
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 08/11] x86: AMD SEV-ES: Handle CPUID #VC vsntk18
2024-06-05 16:07 ` Sean Christopherson
2024-06-06 18:59 ` Vasant Karasulli
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 09/11] x86: AMD SEV-ES: Handle MSR #VC vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 10/11] x86: AMD SEV-ES: Handle IOIO #VC vsntk18
2024-06-05 16:08 ` Sean Christopherson
2024-06-06 19:01 ` Vasant Karasulli
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 11/11] x86: AMD SEV-ES: Handle string IO for " vsntk18
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=20240419161623.45842-4-vsntk18@gmail.com \
--to=vsntk18@gmail.com \
--cc=andrew.jones@linux.dev \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=papaluri@amd.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=varad.gautam@suse.com \
--cc=vkarasulli@suse.de \
/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