Am 12.08.2011 um 09:43 schrieb David Gibson :
> On Fri, Aug 12, 2011 at 07:35:42AM +0200, Alexander Graf wrote:
>>
>> Am 12.08.2011 um 05:33 schrieb David Gibson :
>>
>>> On Tue, Aug 09, 2011 at 06:31:47PM +0200, Alexander Graf wrote:
PAPR defines hypercalls as SC1 instructions. Using thes
On Fri, Aug 12, 2011 at 07:35:42AM +0200, Alexander Graf wrote:
>
> Am 12.08.2011 um 05:33 schrieb David Gibson :
>
> > On Tue, Aug 09, 2011 at 06:31:47PM +0200, Alexander Graf wrote:
> >> PAPR defines hypercalls as SC1 instructions. Using these, the guest
> >> modifies
> >> page tables and does
Am 12.08.2011 um 05:33 schrieb David Gibson :
> On Tue, Aug 09, 2011 at 06:31:47PM +0200, Alexander Graf wrote:
>> PAPR defines hypercalls as SC1 instructions. Using these, the guest modifies
>> page tables and does other privileged operations that it wouldn't be allowed
>> to do in supervisor mo
On Tue, Aug 09, 2011 at 06:31:47PM +0200, Alexander Graf wrote:
> PAPR defines hypercalls as SC1 instructions. Using these, the guest modifies
> page tables and does other privileged operations that it wouldn't be allowed
> to do in supervisor mode.
>
> This patch adds support for PR KVM to trap t
PAPR defines hypercalls as SC1 instructions. Using these, the guest modifies
page tables and does other privileged operations that it wouldn't be allowed
to do in supervisor mode.
This patch adds support for PR KVM to trap these instructions and route them
through the same PAPR hypercall interface
