This enables userspace to get and set various SPRs (special-purpose
registers) using the KVM_[GS]ET_ONE_REG ioctls. With this, userspace
can get and set all the SPRs that are part of the guest state, either
through the KVM_[GS]ET_REGS ioctls, the KVM_[GS]ET_SREGS ioctls, or
the KVM_[GS]ET_ONE_REG
The PAPR paravirtualization interface lets guests register three
different types of per-vCPU buffer areas in its memory for communication
with the hypervisor. These are called virtual processor areas (VPAs).
Currently the hypercalls to register and unregister VPAs are handled
by KVM in the kernel,
This enables userspace to get and set all the guest floating-point
state using the KVM_[GS]ET_ONE_REG ioctls. The floating-point state
includes all of the traditional floating-point registers and the
FPSCR (floating point status/control register), all the VMX/Altivec
vector registers and the VSCR
On 09/25/2012 02:44:52 AM, Alexander Graf wrote:
On 23.08.2012, at 03:03, Scott Wood wrote:
> Avoid a race as described in the code comment.
>
> Also remove a related smp_wmb() from booke's
kvmppc_prepare_to_enter().
> I can't see any reason for it, and the book3s_pr version doesn't
have it
On 25.09.2012, at 11:44, Paul Mackerras wrote:
> This enables userspace to get and set various SPRs (special-purpose
> registers) using the KVM_[GS]ET_ONE_REG ioctls. With this, userspace
> can get and set all the SPRs that are part of the guest state, either
> through the KVM_[GS]ET_REGS ioctls
On 25.09.2012, at 13:06, Jan Kiszka wrote:
> On 2012-09-25 12:58, Alexander Graf wrote:
>>
>> On 25.09.2012, at 12:56, Jan Kiszka wrote:
>>
>>> On 2012-09-25 12:47, Alexander Graf wrote:
On 25.09.2012, at 12:38, Jan Kiszka wrote:
> On 2012-09-24 16:46, Alexander Graf wrote:
On 2012-09-25 12:58, Alexander Graf wrote:
>
> On 25.09.2012, at 12:56, Jan Kiszka wrote:
>
>> On 2012-09-25 12:47, Alexander Graf wrote:
>>>
>>> On 25.09.2012, at 12:38, Jan Kiszka wrote:
>>>
On 2012-09-24 16:46, Alexander Graf wrote:
>
> On 07.09.2012, at 00:56, Scott Wood wrote:
>
On 25.09.2012, at 12:56, Jan Kiszka wrote:
> On 2012-09-25 12:47, Alexander Graf wrote:
>>
>> On 25.09.2012, at 12:38, Jan Kiszka wrote:
>>
>>> On 2012-09-24 16:46, Alexander Graf wrote:
On 07.09.2012, at 00:56, Scott Wood wrote:
> On 09/06/2012 09:56 AM, Bhushan Bharat-R65
On 2012-09-25 12:47, Alexander Graf wrote:
>
> On 25.09.2012, at 12:38, Jan Kiszka wrote:
>
>> On 2012-09-24 16:46, Alexander Graf wrote:
>>>
>>> On 07.09.2012, at 00:56, Scott Wood wrote:
>>>
On 09/06/2012 09:56 AM, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
On 2012-09-24 16:46, Alexander Graf wrote:
>
> On 07.09.2012, at 00:56, Scott Wood wrote:
>
>> On 09/06/2012 09:56 AM, Bhushan Bharat-R65777 wrote:
>>>
>>>
-Original Message-
From: Wood Scott-B07421
Sent: Thursday, September 06, 2012 4:57 AM
To: Bhushan Bharat-R65777
>
On 25.09.2012, at 12:38, Jan Kiszka wrote:
> On 2012-09-24 16:46, Alexander Graf wrote:
>>
>> On 07.09.2012, at 00:56, Scott Wood wrote:
>>
>>> On 09/06/2012 09:56 AM, Bhushan Bharat-R65777 wrote:
> -Original Message-
> From: Wood Scott-B07421
> Sent: Thursday, S
This enables userspace to get and set various SPRs (special-purpose
registers) using the KVM_[GS]ET_ONE_REG ioctls. With this, userspace
can get and set all the SPRs that are part of the guest state, either
through the KVM_[GS]ET_REGS ioctls, the KVM_[GS]ET_SREGS ioctls, or
the KVM_[GS]ET_ONE_REG
The PAPR paravirtualization interface lets guests register three
different types of per-vCPU buffer areas in its memory for communication
with the hypervisor. These are called virtual processor areas (VPAs).
Currently the hypercalls to register and unregister VPAs are handled
by KVM in the kernel,
This enables userspace to get and set all the guest floating-point
state using the KVM_[GS]ET_ONE_REG ioctls. The floating-point state
includes all of the traditional floating-point registers and the
FPSCR (floating point status/control register), all the VMX/Altivec
vector registers and the VSCR
On 23.08.2012, at 03:04, Scott Wood wrote:
> This was found by kmemleak.
>
> Signed-off-by: Scott Wood
Thanks, applied to kvm-ppc-next.
Alex
> ---
> arch/powerpc/kvm/e500_tlb.c |2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/powerpc/kvm/e500_tlb.c b/arch/powerpc/kvm/e500_
On 23.08.2012, at 03:04, Scott Wood wrote:
> We were only allocating half the bytes we need, which was made more
> obvious by a recent fix to the memset in clear_tlb1_bitmap().
>
> Signed-off-by: Scott Wood
Thanks, applied to kvm-ppc-next.
Avi, Marcelo, this one should get applied to anythin
On 23.08.2012, at 03:03, Scott Wood wrote:
> Avoid a race as described in the code comment.
>
> Also remove a related smp_wmb() from booke's kvmppc_prepare_to_enter().
> I can't see any reason for it, and the book3s_pr version doesn't have it.
>
> Signed-off-by: Scott Wood
Does this patch add
17 matches
Mail list logo