From: "Singh, Brijesh" <brijesh.singh@amd.com>
To: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: "Singh, Brijesh" <brijesh.singh@amd.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Joerg Roedel" <joro@8bytes.org>, "Borislav Petkov" <bp@suse.de>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v1 02/10] KVM: SVM: Add KVM_SEND_UPDATE_DATA command
Date: Mon, 29 Apr 2019 16:54:08 +0000 [thread overview]
Message-ID: <0883651a-ac95-022a-1a16-978ddb2cc35d@amd.com> (raw)
In-Reply-To: <c0cf8d9b-4b47-f578-bc51-29739a3c2f8d@amd.com>
On 4/26/19 3:31 PM, Lendacky, Thomas wrote:
...
>>
>> static unsigned int max_sev_asid;
>> static unsigned int min_sev_asid;
>> +static unsigned long me_mask;
>
> sev_me_mask ?
>
Agreed.
>> static unsigned long *sev_asid_bitmap;
>> #define __sme_page_pa(x) __sme_set(page_to_pfn(x) << PAGE_SHIFT)
>>
>> @@ -1216,15 +1217,21 @@ static int avic_ga_log_notifier(u32 ga_tag)
>> static __init int sev_hardware_setup(void)
>> {
>> struct sev_user_data_status *status;
>> + int eax, ebx;
>> int rc;
>>
>> - /* Maximum number of encrypted guests supported simultaneously */
>> - max_sev_asid = cpuid_ecx(0x8000001F);
>> + /*
>> + * Query the memory encryption information.
>> + * EBX: Bit 0:5 Pagetable bit position used to indicate encryption (aka Cbit).
>> + * ECX: Maximum number of encrypted guests supported simultaneously.
>> + * EDX: Minimum ASID value that should be used for SEV guest.
>> + */
>> + cpuid(0x8000001f, &eax, &ebx, &max_sev_asid, &min_sev_asid);
>>
>> if (!max_sev_asid)
>> return 1;
>>
>> - /* Minimum ASID value that should be used for SEV guest */
>> + me_mask = 1UL << (ebx & 0x3f);
>> min_sev_asid = cpuid_edx(0x8000001F);
>
> You can remove this since you obtained it with the cpuid() call above.
>
I thought I removed it but.. I will take care in next rev.
>>
>> /* Initialize SEV ASID bitmap */
>> @@ -7053,6 +7060,118 @@ static int sev_send_start(struct kvm *kvm, struct kvm_sev_cmd *argp)
>> return ret;
>> }
>>
>> +static int sev_send_update_data(struct kvm *kvm, struct kvm_sev_cmd *argp)
>> +{
>> + struct kvm_sev_info *sev = &to_kvm_svm(kvm)->sev_info;
>> + struct sev_data_send_update_data *data;
>> + struct kvm_sev_send_update_data params;
>> + void *hdr = NULL, *trans_data = NULL;
>> + struct page **guest_page = NULL;
>> + unsigned long n;
>> + int ret, offset;
>> +
>> + if (!sev_guest(kvm))
>> + return -ENOTTY;
>> +
>> + if (copy_from_user(¶ms, (void __user *)(uintptr_t)argp->data,
>> + sizeof(struct kvm_sev_send_update_data)))
>> + return -EFAULT;
>> +
>> + data = kzalloc(sizeof(*data), GFP_KERNEL);
>> + if (!data)
>> + return -ENOMEM;
>> +
>> + /* userspace wants to query either header or trans length */
>> + if (!params.trans_len || !params.hdr_len)
>> + goto cmd;
>> +
>> + ret = -EINVAL;
>> + if (!params.trans_uaddr || !params.guest_uaddr ||
>> + !params.guest_len || !params.hdr_uaddr)
>> + goto e_free;
>> +
>> + /* Check if we are crossing the page boundry */
>> + ret = -EINVAL;
>> + offset = params.guest_uaddr & (PAGE_SIZE - 1);
>> + if ((params.guest_len + offset > PAGE_SIZE))
>> + goto e_free;
>> +
>> + ret = -ENOMEM;
>> + hdr = kmalloc(params.hdr_len, GFP_KERNEL);
>> + if (!hdr)
>> + goto e_free;
>> +
>> + data->hdr_address = __psp_pa(hdr);
>> + data->hdr_len = params.hdr_len;
>> +
>> + ret = -ENOMEM;
>> + trans_data = kmalloc(params.trans_len, GFP_KERNEL);
>> + if (!trans_data)
>> + goto e_free;
>> +
>> + data->trans_address = __psp_pa(trans_data);
>> + data->trans_len = params.trans_len;
>> +
>> + /* Pin guest memory */
>> + ret = -EFAULT;
>> + guest_page = sev_pin_memory(kvm, params.guest_uaddr & PAGE_MASK,
>> + PAGE_SIZE, &n, 0);
>> + if (!guest_page)
>> + goto e_free;
>> +
>> + data->guest_address = __sme_page_pa(guest_page[0]) + offset;
>
> If the C-bit needs to be set regardless below, then you don't need the
> __sme version of this.
>
Noted.
next prev parent reply other threads:[~2019-04-29 16:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 16:09 [RFC PATCH v1 00/10] Add AMD SEV guest live migration support Singh, Brijesh
2019-04-24 16:09 ` [RFC PATCH v1 01/10] KVM: SVM: Add KVM_SEV SEND_START command Singh, Brijesh
2019-04-26 14:10 ` Borislav Petkov
2019-04-26 14:29 ` Singh, Brijesh
2019-04-26 20:43 ` Borislav Petkov
2019-04-29 15:01 ` Singh, Brijesh
2019-04-29 16:36 ` Borislav Petkov
2019-04-29 16:43 ` Singh, Brijesh
2019-04-24 16:10 ` [RFC PATCH v1 02/10] KVM: SVM: Add KVM_SEND_UPDATE_DATA command Singh, Brijesh
2019-04-26 20:31 ` Lendacky, Thomas
2019-04-29 16:54 ` Singh, Brijesh [this message]
2019-04-24 16:10 ` [RFC PATCH v1 03/10] KVM: SVM: Add KVM_SEV_SEND_FINISH command Singh, Brijesh
2019-04-24 16:10 ` [RFC PATCH v1 04/10] KVM: SVM: Add support for KVM_SEV_RECEIVE_START command Singh, Brijesh
2019-04-26 21:08 ` Lendacky, Thomas
2019-04-24 16:10 ` [RFC PATCH v1 05/10] KVM: SVM: Add KVM_SEV_RECEIVE_UPDATE_DATA command Singh, Brijesh
2019-04-26 21:11 ` Lendacky, Thomas
2019-04-24 16:10 ` [RFC PATCH v1 06/10] KVM: SVM: Add KVM_SEV_RECEIVE_FINISH command Singh, Brijesh
2019-04-26 21:11 ` Lendacky, Thomas
2019-04-24 16:10 ` [RFC PATCH v1 07/10] KVM: x86: Add AMD SEV specific Hypercall3 Singh, Brijesh
2019-04-24 16:10 ` [RFC PATCH v1 08/10] KVM: X86: Introduce KVM_HC_PAGE_ENC_STATUS hypercall Singh, Brijesh
2019-04-26 21:39 ` Lendacky, Thomas
2019-05-03 14:25 ` Singh, Brijesh
2019-04-24 16:10 ` [RFC PATCH v1 09/10] KVM: x86: Introduce KVM_GET_PAGE_ENC_BITMAP ioctl Singh, Brijesh
2019-04-24 16:10 ` [RFC PATCH v1 10/10] mm: x86: Invoke hypercall when page encryption status is changed Singh, Brijesh
2019-04-24 19:15 ` [RFC PATCH v1 00/10] Add AMD SEV guest live migration support Steve Rutherford
2019-04-24 21:32 ` Singh, Brijesh
[not found] ` <CABayD+fy5+QNU8YWsVrfd6jyvPo3AWCBgR-V8iWKzZkWxQY=zA@mail.gmail.com>
2019-04-25 2:15 ` Singh, Brijesh
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=0883651a-ac95-022a-1a16-978ddb2cc35d@amd.com \
--to=brijesh.singh@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--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