Displaying 8 results from an estimated 8 matches for "update_intr_g".
2017 Nov 17
2
[PATCH RFC v3 3/6] sched/idle: Add a generic poll before enter real idle path
..._call())..
thanks Xen guys, who has implemented the paravirt framework. I can
implement it
as easy as following:
???????????? --- a/arch/x86/kernel/kvm.c
???????????? +++ b/arch/x86/kernel/kvm.c
???????????? @@ -465,6 +465,12 @@ static void __init
kvm_apf_trap_init(void)
???????????????????? update_intr_gate(X86_TRAP_PF, async_page_fault);
????????????? }
???????????? +static __cpuidle void kvm_safe_halt(void)
???????????? +{
??? ???? +??????? /* 1. POLL, if need_resched() --> return */
??? ???? +
???????????? +??????? asm volatile("sti; hlt": : :"memory"); /* 2. halt *...
2017 Nov 17
2
[PATCH RFC v3 3/6] sched/idle: Add a generic poll before enter real idle path
..._call())..
thanks Xen guys, who has implemented the paravirt framework. I can
implement it
as easy as following:
???????????? --- a/arch/x86/kernel/kvm.c
???????????? +++ b/arch/x86/kernel/kvm.c
???????????? @@ -465,6 +465,12 @@ static void __init
kvm_apf_trap_init(void)
???????????????????? update_intr_gate(X86_TRAP_PF, async_page_fault);
????????????? }
???????????? +static __cpuidle void kvm_safe_halt(void)
???????????? +{
??? ???? +??????? /* 1. POLL, if need_resched() --> return */
??? ???? +
???????????? +??????? asm volatile("sti; hlt": : :"memory"); /* 2. halt *...
2017 Nov 17
0
[PATCH RFC v3 3/6] sched/idle: Add a generic poll before enter real idle path
...t
> it
> as easy as following:
>
> ???????????? --- a/arch/x86/kernel/kvm.c
Your email client is using a very strange formatting.
> ???????????? +++ b/arch/x86/kernel/kvm.c
> ???????????? @@ -465,6 +465,12 @@ static void __init kvm_apf_trap_init(void)
> ???????????????????? update_intr_gate(X86_TRAP_PF, async_page_fault);
> ????????????? }
>
> ???????????? +static __cpuidle void kvm_safe_halt(void)
> ???????????? +{
> ??? ???? +??????? /* 1. POLL, if need_resched() --> return */
> ??? ???? +
> ???????????? +??????? asm volatile("sti; hlt": : :&quo...
2017 Nov 16
1
[PATCH RFC v3 3/6] sched/idle: Add a generic poll before enter real idle path
On 2017-11-16 06:03, Thomas Gleixner wrote:
> On Wed, 15 Nov 2017, Peter Zijlstra wrote:
>
>> On Mon, Nov 13, 2017 at 06:06:02PM +0800, Quan Xu wrote:
>>> From: Yang Zhang <yang.zhang.wz at gmail.com>
>>>
>>> Implement a generic idle poll which resembles the functionality
>>> found in arch/. Provide weak arch_cpu_idle_poll function which
2020 Apr 28
116
[PATCH v3 00/75] x86: SEV-ES Guest Support
Hi,
here is the next version of changes to enable Linux to run as an SEV-ES
guest. The code was rebased to v5.7-rc3 and got a fair number of changes
since the last version.
What is SEV-ES
==============
SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted
State' and means a hardware feature of AMD processors which hides the
register state of VCPUs to the hypervisor by
2020 Apr 28
116
[PATCH v3 00/75] x86: SEV-ES Guest Support
Hi,
here is the next version of changes to enable Linux to run as an SEV-ES
guest. The code was rebased to v5.7-rc3 and got a fair number of changes
since the last version.
What is SEV-ES
==============
SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted
State' and means a hardware feature of AMD processors which hides the
register state of VCPUs to the hypervisor by
2020 Feb 11
83
[RFC PATCH 00/62] Linux as SEV-ES Guest Support
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.
2020 Feb 11
83
[RFC PATCH 00/62] Linux as SEV-ES Guest Support
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.