linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tianyu Lan <ltykernel@gmail.com>
To: Wei Liu <wei.liu@kernel.org>,
	Saurabh Singh Sengar <ssengar@microsoft.com>
Cc: KY Srinivasan <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Dexuan Cui <decui@microsoft.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"bp@alien8.de" <bp@alien8.de>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"Michael Kelley (LINUX)" <mikelley@microsoft.com>,
	Tianyu Lan <Tianyu.Lan@microsoft.com>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"vkuznets@redhat.com" <vkuznets@redhat.com>
Subject: Re: [EXTERNAL] [PATCH V2 2/9] x86/hyperv: Set Virtual Trust Level in VMBus init message
Date: Fri, 11 Aug 2023 00:22:36 +0800	[thread overview]
Message-ID: <da667608-a8aa-f5b8-1621-de29b3f19272@gmail.com> (raw)
In-Reply-To: <ZNB3m6Qiml7JDTQ7@liuwe-devbox-debian-v2>

On 8/7/2023 12:48 PM, Wei Liu wrote:
> On Fri, Jul 07, 2023 at 09:07:54AM +0000, Saurabh Singh Sengar wrote:
>>
>>
>>> +
>>> +	ret = hv_do_hypercall(control, input, output);
>>> +	if (hv_result_success(ret))
>>> +		vtl = output->as64.low & HV_X64_VTL_MASK;
>>> +	else
>>> +		pr_err("Hyper-V: failed to get VTL! %lld", ret);
>>
>> In case of error this function will return vtl=0, which can be the valid value of vtl.
>> I suggest we initialize vtl with -1 so and then check for its return.
>>
>> This could be a good utility function which can be used for any Hyper-V VTL system, so think
>> of making it global ?
>>
> 
> Tianyu -- your thought on this?

In current user cases, the guest only runs in VTL0 and Hyper-V may
return VTL error in some cases but kernel still may run with 0 as VTL.

I just sent out v5 and set VTL to 0 by default if fail to get VTL from
Hyper-V and give out a warning log. The get_vtl() is only called on 
enlightened SEV-SNP guest. If there is new case that needs handle the 
error from Hyper-V when call VTL hvcall, we may add the logic later.

  reply	other threads:[~2023-08-10 16:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  3:22 [PATCH V2 0/9] x86/hyperv: Add AMD sev-snp enlightened guest support on hyperv Tianyu Lan
2023-06-27  3:22 ` [PATCH V2 1/9] x86/hyperv: Add sev-snp enlightened guest static key Tianyu Lan
2023-07-04 14:17   ` Michael Kelley (LINUX)
2023-07-05 14:43     ` Tianyu Lan
2023-06-27  3:22 ` [PATCH V2 2/9] x86/hyperv: Set Virtual Trust Level in VMBus init message Tianyu Lan
2023-07-04 14:18   ` Michael Kelley (LINUX)
2023-07-07  9:07   ` [EXTERNAL] " Saurabh Singh Sengar
2023-08-07  4:48     ` Wei Liu
2023-08-10 16:22       ` Tianyu Lan [this message]
2023-08-11  2:55         ` Saurabh Singh Sengar
2023-06-27  3:22 ` [PATCH V2 3/9] x86/hyperv: Mark Hyper-V vp assist page unencrypted in SEV-SNP enlightened guest Tianyu Lan
2023-07-04 14:18   ` Michael Kelley (LINUX)
2023-06-27  3:22 ` [PATCH V2 4/9] drivers: hv: Mark percpu hvcall input arg " Tianyu Lan
2023-07-04 14:19   ` Michael Kelley (LINUX)
2023-06-27  3:22 ` [PATCH V2 5/9] x86/hyperv: Use vmmcall to implement Hyper-V hypercall in sev-snp " Tianyu Lan
2023-06-27  3:22 ` [PATCH V2 6/9] clocksource: hyper-v: Mark hyperv tsc page unencrypted " Tianyu Lan
2023-07-04 14:19   ` Michael Kelley (LINUX)
2023-06-27  3:22 ` [PATCH V2 7/9] x86/hyperv: Initialize cpu and memory for SEV-SNP " Tianyu Lan
2023-07-04 14:23   ` Michael Kelley (LINUX)
2023-06-27  3:22 ` [PATCH V2 8/9] x86/hyperv: Add smp support for SEV-SNP guest Tianyu Lan
2023-07-04 14:24   ` Michael Kelley (LINUX)
2023-06-27  3:22 ` [PATCH V2 9/9] x86/hyperv: Add hyperv-specific handling for VMMCALL under SEV-ES Tianyu Lan
2023-07-04 14:25   ` Michael Kelley (LINUX)

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=da667608-a8aa-f5b8-1621-de29b3f19272@gmail.com \
    --to=ltykernel@gmail.com \
    --cc=Tianyu.Lan@microsoft.com \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=kys@microsoft.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=mingo@redhat.com \
    --cc=ssengar@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=wei.liu@kernel.org \
    --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).