On 24.11.2012, at 10:32, Paul Mackerras wrote:
> On Sat, Nov 24, 2012 at 10:05:37AM +0100, Alexander Graf wrote:
>>
>>
>> On 23.11.2012, at 23:13, Paul Mackerras wrote:
>>
>>> On Fri, Nov 23, 2012 at 04:47:45PM +0100, Alexander Graf wrote:
On 22.11.2012, at 10:28, Paul Mackerras wr
On Sat, Nov 24, 2012 at 10:05:37AM +0100, Alexander Graf wrote:
>
>
> On 23.11.2012, at 23:13, Paul Mackerras wrote:
>
> > On Fri, Nov 23, 2012 at 04:47:45PM +0100, Alexander Graf wrote:
> >>
> >> On 22.11.2012, at 10:28, Paul Mackerras wrote:
> >>
> >>> Currently, if the guest does an H_PROT
On 23.11.2012, at 23:13, Paul Mackerras wrote:
> On Fri, Nov 23, 2012 at 04:47:45PM +0100, Alexander Graf wrote:
>>
>> On 22.11.2012, at 10:28, Paul Mackerras wrote:
>>
>>> Currently, if the guest does an H_PROTECT hcall requesting that the
>>> permissions on a HPT entry be changed to allow w
On Fri, Nov 23, 2012 at 04:47:45PM +0100, Alexander Graf wrote:
>
> On 22.11.2012, at 10:28, Paul Mackerras wrote:
>
> > Currently, if the guest does an H_PROTECT hcall requesting that the
> > permissions on a HPT entry be changed to allow writing, we make the
> > requested change even if the pag
On 22.11.2012, at 10:28, Paul Mackerras wrote:
> Currently, if the guest does an H_PROTECT hcall requesting that the
> permissions on a HPT entry be changed to allow writing, we make the
> requested change even if the page is marked read-only in the host
> Linux page tables. This is a problem si