Re: [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write
From: Alexey Kardashevskiy <aik@xxxxxxx>
Date: Tue, 24 Jan 2023 23:37:46 +1100
Cc: kvm@xxxxxxxxxxxxxxx, x86@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Yury Norov <yury.norov@xxxxxxxxx>, Venu Busireddy <venu.busireddy@xxxxxxxxxx>, Tony Luck <tony.luck@xxxxxxxxx>, Tom Lendacky <thomas.lendacky@xxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Sean Christopherson <seanjc@xxxxxxxxxx>, Sandipan Das <sandipan.das@xxxxxxx>, Pawan Gupta <pawan.kumar.gupta@xxxxxxxxxxxxxxx>, Paolo Bonzini <pbonzini@xxxxxxxxxx>, Michael Roth <michael.roth@xxxxxxx>, Mario Limonciello <mario.limonciello@xxxxxxx>, Kim Phillips <kim.phillips@xxxxxxx>, Kees Cook <keescook@xxxxxxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Jakub Kicinski <kuba@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>, Daniel Sneddon <daniel.sneddon@xxxxxxxxxxxxxxx>, Brijesh Singh <brijesh.singh@xxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Alexander Shishkin <alexander.shishkin@xxxxxxxxxxxxxxx>, Adrian Hunter <adrian.hunter@xxxxxxxxx>, "Peter Zijlstra (Intel)" <peterz@xxxxxxxxxxxxx>, "Jason A. Donenfeld" <Jason@xxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>
In-reply-to: <b30d6f61-2dc9-4c4f-dbdb-a48c186745d3@amd.com>
References: <20230120031047.628097-1-aik@amd.com> <20230120031047.628097-4-aik@amd.com> <adc11ed3-de89-a389-e629-3c951257469c@amd.com> <533c5c83-b68b-eff0-d36d-9963194ab844@amd.com> <b30d6f61-2dc9-4c4f-dbdb-a48c186745d3@amd.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1

On 24/1/23 21:37, Nikunj A. Dadhania wrote:>> It isMSR_AMD64_SEV_DEBUG_SWAP (SEV, not SNP), it is an SEV-ES thing.> Yes,noticed that, earlier analysis was that Debug Swap shouldn't need anyguest side changes, but it does need it.>>> Why is that featurenegotiation SNP-only and not SEV?> > As per the spec, GHCB terminationrequest: reason code: 0x2 is SNP features specific.Does the guest really need to terminate in such case? A VM could justnot do the GHCB thing if it does not want to.



--
Alexey

Follow-Ups:
- Re: [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write
  - From: Nikunj A. Dadhania

References:
- [PATCH kernel v3 0/3] KVM: SEV: Enable AMD SEV-ES DebugSwap
  - From: Alexey Kardashevskiy
- [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write
  - From: Alexey Kardashevskiy
- Re: [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write
  - From: Nikunj A. Dadhania
- Re: [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write
  - From: Alexey Kardashevskiy
- Re: [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write
  - From: Nikunj A. Dadhania

Prev by Date: Re: [PATCH 24/32] acpi: Move the QMP command from monitor/ to hw/acpi/
Next by Date: Re: [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write
Previous by thread: Re: [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write
Next by thread: Re: [PATCH kernel v3 3/3] x86/sev: Do not handle #VC for DR7 read/write
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]