From: Avi Kivity <avi@qumranet.com>
To: kvm-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, mingo@elte.hu
Subject: [PATCH] KVM: AMD SVM: Avoid three more new instructions
Date: Tue, 28 Nov 2006 13:13:45 -0000 [thread overview]
Message-ID: <20061128131345.2356525015E@cleopatra.q> (raw)
The clgi, stgi, and invlpga instructions are all too new to unleash on
the world's assemblers. Replace them with the opcode sequences.
Signed-off-by: Avi Kivity <avi@qumranet.com>
diff -X /home/avi/kvm/linux-2.6/Documentation/dontdiff --exclude=Makefile -ru /home/avi/kvm/linux-2.6/drivers/kvm/svm.c /home/avi/kvm-release/kernel/svm.c
--- linux-2.6/drivers/kvm/svm.c 2006-11-28 14:31:03.000000000 +0200
+++ linux-2.6/drivers/kvm/svm.c 2006-11-28 15:08:19.000000000 +0200
@@ -102,17 +102,17 @@
static inline void clgi(void)
{
- asm volatile ("clgi");
+ asm volatile (SVM_CLGI);
}
static inline void stgi(void)
{
- asm volatile ("stgi");
+ asm volatile (SVM_STGI);
}
static inline void invlpga(unsigned long addr, u32 asid)
{
- asm volatile ("invlpga" :: "a"(addr), "c"(asid));
+ asm volatile (SVM_INVLPGA :: "a"(addr), "c"(asid));
}
static inline unsigned long read_cr2(void)
diff -X /home/avi/kvm/linux-2.6/Documentation/dontdiff --exclude=Makefile -ru /home/avi/kvm/linux-2.6/drivers/kvm/svm.h /home/avi/kvm-release/kernel/svm.h
--- linux-2.6/drivers/kvm/svm.h 2006-11-28 14:14:17.000000000 +0200
+++ linux-2.6/drivers/kvm/svm.h 2006-11-28 15:09:17.000000000 +0200
@@ -307,6 +307,9 @@
#define SVM_VMLOAD ".byte 0x0f, 0x01, 0xda"
#define SVM_VMRUN ".byte 0x0f, 0x01, 0xd8"
#define SVM_VMSAVE ".byte 0x0f, 0x01, 0xdb"
+#define SVM_CLGI ".byte 0x0f, 0x01, 0xdd"
+#define SVM_STGI ".byte 0x0f, 0x01, 0xdc"
+#define SVM_INVLPGA ".byte 0x0f, 0x01, 0xdf"
#endif
reply other threads:[~2006-11-28 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061128131345.2356525015E@cleopatra.q \
--to=avi@qumranet.com \
--cc=akpm@osdl.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®