search for: running_on_sev_es

...> instructions. As a general comment on all of these event handlers: Why do we bother having the hypercalls in the interrupt handler as opposed to just calling them directly. What you have is: wrmsr() -> #VC exception hcall() But we could make our rd/wrmsr() wrappers just do: if (running_on_sev_es()) hcall(HCALL_MSR_WHATEVER...) else wrmsr() and then we don't have any of the nastiness of exception handling.

...> instructions. As a general comment on all of these event handlers: Why do we bother having the hypercalls in the interrupt handler as opposed to just calling them directly. What you have is: wrmsr() -> #VC exception hcall() But we could make our rd/wrmsr() wrappers just do: if (running_on_sev_es()) hcall(HCALL_MSR_WHATEVER...) else wrmsr() and then we don't have any of the nastiness of exception handling.

...f these event handlers: Why do we bother > having the hypercalls in the interrupt handler as opposed to just > calling them directly. What you have is: > > wrmsr() > -> #VC exception > hcall() > > But we could make our rd/wrmsr() wrappers just do: > > if (running_on_sev_es()) > hcall(HCALL_MSR_WHATEVER...) > else > wrmsr() > > and then we don't have any of the nastiness of exception handling. Yes, investigating this is on the list for future optimizations (besides caching CPUID results). My idea is to use alternatives patching for this. But...

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.