From: Vasant Karasulli <vkarasulli@suse.de>
To: linux-kernel@vger.kernel.org
Cc: bp@alien8.de, jroedel@suse.de, kvm@vger.kernel.org,
x86@kernel.org, thomas.lendacky@amd.com,
Vasant Karasulli <vkarasulli@suse.de>
Subject: [PATCH v5 0/1] x86/test: Add a test for AMD SEV-ES #VC handling
Date: Tue, 8 Feb 2022 17:26:22 +0100 [thread overview]
Message-ID: <20220208162623.18368-1-vkarasulli@suse.de> (raw)
Hello!
This is the version 5 of the patch written to add a test for
AMD SEV-ES #VC handling. This version attempts to
address review comments to the previous version of the patch in
https://lore.kernel.org/kvm/YNRgHbPVGpLaByjH@zn.tnic/.
Following changes have been made to address the comments:
1. Changed the subject to x86/test from x86.
2. In file arch/x86/Kconfig.debug enclosed the config AMD_SEV_TEST_VC
inside the guard X86_TESTS.
3. Renamed the test file to sev-test-vc.c to indicate that
file includes all the #VC handling related tests.
4. Memory barries are apparently not necessary and have been removed.
Thanks,
Vasant
----------------------------------------------------------------------
arch/x86/Kbuild | 2 +
arch/x86/Kconfig.debug | 16 ++++
arch/x86/kernel/Makefile | 7 ++
arch/x86/tests/Makefile | 3 +
arch/x86/tests/sev-test-vc.c | 154 +++++++++++++++++++++++++++++++++++
5 files changed, 182 insertions(+)
create mode 100644 arch/x86/tests/Makefile
create mode 100644 arch/x86/tests/sev-test-vc.c
base-commit: dfd42facf1e4ada021b939b4e19c935dcdd55566
prerequisite-patch-id: 660950af15f9a972b1f71aa7702ebebe7dd9636b
prerequisite-patch-id: 9635b44cd178a2ee20d83acbc7a07101fd7e81a3
prerequisite-patch-id: 3a7cfa2a885ad20a9f325febcbe31ef53b41e0b1
prerequisite-patch-id: 5e48ede5d4df9de5df3d483874b4aa1711b5dcf0
prerequisite-patch-id: b66ebf185fceb6e8e98b466c974ed777f0200787
prerequisite-patch-id: d5bde21908fbada516dc757e29c6ad70926ab5bf
prerequisite-patch-id: ed38b7fc213fa66845dc25502f18b79e3dc907db
prerequisite-patch-id: 053546f9741643d742f5149c8441f8484e1918d1
prerequisite-patch-id: a20f9a6fd1ad2db0bae2550d5442d7275c481b01
prerequisite-patch-id: bde103392dd4c0a5c360446dbc8d2e5f82671575
prerequisite-patch-id: af44d5e0a6f51e1fe5cf6aef7d0be36e201663b4
prerequisite-patch-id: 952ebde20c8c084f43523f8230ced76beae08b3e
prerequisite-patch-id: 0b295c1545756626a9bca5bce8be4557742b7a56
prerequisite-patch-id: 98bf6777201eeab52938c28de1090387d454ef55
prerequisite-patch-id: d64628531375578e4bc6de3bcba1a3de658e28d8
prerequisite-patch-id: 752ea9954abeb624b803ad86e4974769f97ddd6e
--
2.32.0
next reply other threads:[~2022-02-08 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 16:26 Vasant Karasulli [this message]
2022-02-08 16:26 ` [PATCH v5 1/1] x86/test: Add a test for AMD SEV-ES #VC handling Vasant Karasulli
2022-03-17 13:21 ` Joerg Roedel
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=20220208162623.18368-1-vkarasulli@suse.de \
--to=vkarasulli@suse.de \
--cc=bp@alien8.de \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.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).