From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it, Nicolai Stange <nstange@suse.de>
Subject: Re: [LTP] [PATCH 1/7] KVM: Add VMSAVE/VMLOAD intercept constants
Date: Thu, 18 May 2023 00:08:27 +0200 [thread overview]
Message-ID: <20230517220827.GA8914@pevik> (raw)
In-Reply-To: <20230517153642.26919-2-mdoucha@suse.cz>
Hi Martin,
> Signed-off-by: Martin Doucha <mdoucha@suse.cz>
> ---
> testcases/kernel/kvm/include/kvm_x86_svm.h | 5 +++++
> 1 file changed, 5 insertions(+)
> diff --git a/testcases/kernel/kvm/include/kvm_x86_svm.h b/testcases/kernel/kvm/include/kvm_x86_svm.h
> index 965d1e716..3eb832849 100644
> --- a/testcases/kernel/kvm/include/kvm_x86_svm.h
> +++ b/testcases/kernel/kvm/include/kvm_x86_svm.h
> @@ -37,10 +37,15 @@
> /* SVM event intercept IDs */
> #define SVM_INTERCEPT_HLT 0x78
> #define SVM_INTERCEPT_VMRUN 0x80
> +#define SVM_INTERCEPT_VMLOAD 0x82
> +#define SVM_INTERCEPT_VMSAVE 0x83
> #define SVM_INTERCEPT_MAX 0x95
> /* SVM vmrun exit codes */
> #define SVM_EXIT_HLT 0x78
> +#define SVM_EXIT_VMRUN 0x80
> +#define SVM_EXIT_VMLOAD 0x82
> +#define SVM_EXIT_VMSAVE 0x83
It looks like these three aren't used anywhere.
Kind regards,
Petr
> #define SVM_EXIT_AVIC_NOACCEL 0x402
> #define SVM_EXIT_INVALID ((uint64_t)-1)
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-05-17 20:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 15:36 [LTP] [PATCH 0/7] Two AMD SVM vulnerability tests Martin Doucha
2023-05-17 15:36 ` [LTP] [PATCH 1/7] KVM: Add VMSAVE/VMLOAD intercept constants Martin Doucha
2023-05-17 22:08 ` Petr Vorel [this message]
2023-05-18 8:27 ` Martin Doucha
2023-05-18 9:49 ` Petr Vorel
2023-05-17 15:36 ` [LTP] [PATCH 2/7] Add test for CVE 2021-3656 Martin Doucha
2023-05-17 22:32 ` Petr Vorel
2023-05-18 8:29 ` Martin Doucha
2023-05-18 9:56 ` Petr Vorel
2023-05-17 15:36 ` [LTP] [PATCH 3/7] lib: Add safe functions for pthread_kill() and mutexes Martin Doucha
2023-05-17 23:07 ` Petr Vorel
2023-05-23 12:02 ` Cyril Hrubis
2023-05-17 15:36 ` [LTP] [PATCH 4/7] KVM: Add async communication helper functions Martin Doucha
2023-05-17 22:47 ` Petr Vorel
2023-05-18 8:36 ` Martin Doucha
2023-05-18 9:55 ` Petr Vorel
2023-05-23 12:13 ` Cyril Hrubis
2023-05-23 12:18 ` Martin Doucha
2023-05-17 15:36 ` [LTP] [PATCH 5/7] KVM: Allow expected KVM_RUN errors in tst_kvm_run_instance() Martin Doucha
2023-05-18 10:03 ` Petr Vorel
2023-05-23 12:22 ` Cyril Hrubis
2023-05-17 15:36 ` [LTP] [PATCH 6/7] KVM: Add STGI/CLGI intercept constants Martin Doucha
2023-05-17 23:20 ` Petr Vorel
2023-05-18 8:38 ` Martin Doucha
2023-05-18 9:53 ` Petr Vorel
2023-05-17 15:36 ` [LTP] [PATCH 7/7] Add KVM test for CPU lockup through malicous SVM guest Martin Doucha
2023-05-18 10:08 ` Petr Vorel
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=20230517220827.GA8914@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
--cc=nstange@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 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.