On Fri, Aug 12, 2011 at 07:35:42AM +0200, Alexander Graf wrote:
Am 12.08.2011 um 05:33 schrieb David Gibson da...@gibson.dropbear.id.au:
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
Am 12.08.2011 um 09:43 schrieb David Gibson da...@gibson.dropbear.id.au:
On Fri, Aug 12, 2011 at 07:35:42AM +0200, Alexander Graf wrote:
Am 12.08.2011 um 05:33 schrieb David Gibson da...@gibson.dropbear.id.au:
On Tue, Aug 09, 2011 at 06:31:47PM +0200, Alexander Graf wrote:
PAPR defines
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 these
Am 12.08.2011 um 05:33 schrieb David Gibson da...@gibson.dropbear.id.au:
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
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