From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: about memory protection. Date: Sun, 25 Jul 2010 22:43:17 +0300 Message-ID: <4C4C93D5.9070404@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org To: =?UTF-8?B?5ZC05b+g6L+c?= Return-path: Received: from mx1.redhat.com ([209.132.183.28]:27999 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751884Ab0GYTnV (ORCPT ); Sun, 25 Jul 2010 15:43:21 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 07/25/2010 06:07 PM, =E5=90=B4=E5=BF=A0=E8=BF=9C wrote: > i want to set some page of guest wrie protection so that the guest ca= n > not write to this page any more . so i set the corresponding page > write protection. but if guest modify cr0 to clear wp bit. what could > i do to avoid this ? The host keeps cr0.wp=3D1 even if the guest clears it, so write protect= ion=20 from the host works. --=20 I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.