Re: [tip: x86/seves] x86/kvm: Add KVM-specific VMMCALL handling under SEV-ES

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

Subject: Re: [tip: x86/seves] x86/kvm: Add KVM-specific VMMCALL handling under SEV-ES
From: Joerg Roedel <jroedel@xxxxxxx>
Date: Wed, 28 Oct 2020 10:49:52 +0100
Cc: linux-kernel@xxxxxxxxxxxxxxx, "Lendacky, Thomas" <Thomas.Lendacky@xxxxxxx>, linux-tip-commits@xxxxxxxxxxxxxxx, Borislav Petkov <bp@xxxxxxx>, x86 <x86@xxxxxxxxxx>
In-reply-to: <CAAYXXYw7ZKM+4ZCzn_apb4iy07R5VfcYeyus-kc0ETh_vkBkPg@mail.gmail.com>
References: <20200907131613.12703-64-joro@8bytes.org> <159972972598.20229.12880317872521101289.tip-bot2@tip-bot2> <CAAYXXYx=Eq4gYfUqdO7u37VRD_GpPYFQgN=GZySmAMcDc2AM=g@mail.gmail.com> <CAAYXXYw7ZKM+4ZCzn_apb4iy07R5VfcYeyus-kc0ETh_vkBkPg@mail.gmail.com>
User-agent: Mutt/1.10.1 (2018-07-13)

On Tue, Oct 27, 2020 at 04:14:15PM -0700, Erdem Aktas wrote:
> It seems to me that the kvm_sev_es_hcall_prepare is leaking more
> information than it is needed. Is this an expected behavior?

What exactly is leaked? The kvm hypercall uses RAX, RBX, RCX, RDX and
RSI for parameters.

Regards,

	Joerg

Follow-Ups:
- Re: [tip: x86/seves] x86/kvm: Add KVM-specific VMMCALL handling under SEV-ES
  - From: Erdem Aktas

References:
- [tip: x86/seves] x86/kvm: Add KVM-specific VMMCALL handling under SEV-ES
  - From: tip-bot2 for Tom Lendacky
- Re: [tip: x86/seves] x86/kvm: Add KVM-specific VMMCALL handling under SEV-ES
  - From: Erdem Aktas

Prev by Date: Re: [tip: locking/core] lockdep: Fix usage_traceoverflow
Next by Date: Re: [tip: locking/core] lockdep: Fix lockdep recursion
Previous by thread: Re: [tip: x86/seves] x86/kvm: Add KVM-specific VMMCALL handling under SEV-ES
Next by thread: Re: [tip: x86/seves] x86/kvm: Add KVM-specific VMMCALL handling under SEV-ES
Index(es):
- Date
- Thread

[Index of Archives] [Linux Stable Commits] [Linux Stable Kernel] [Linux Kernel] [Linux USB Devel] [Linux Video &Media] [Linux Audio Users] [Yosemite News] [Linux SCSI]