WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] mem_event: Allow memory access listener to perfo

To: Aravindh Puthiyaparambil <aravindh@xxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] mem_event: Allow memory access listener to perform single step execution
From: Keir Fraser <keir@xxxxxxx>
Date: Sat, 28 May 2011 08:53:56 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 28 May 2011 01:26:08 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:user-agent:date:subject:from:to:cc :message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=+6WkNSabST5mxPBSqoP9nu4+MntwTgXSrPFrJ+Orw6s=; b=GLB+jmvZ5U3F6yGgkanfxM//avAYruRsyG51+YA0EBQaB87KZca1gElO4kyDLHpg/+ fZBeeHhFoJadzN5r+O7eNsaLzfVr2rm7HNffeSBTRnZOk8LLp3aRCC/+k9nYucDDz4RY Pn104yU4LOfK6lk5man9SmMmEsDk5jMsgo4mk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=fywff8UwddezU+WLrH8DqkVoKplI+qx8dtXtjhjTQ+AxLYCFf5+KVmyjiP2GKncTEE Of8OowsSBMZIVwfgrylhf5tKTH3ewgFnC2i6TsSHMdI37YeNYv2zqNOhBYgIXYQ4SxE0 H3ED2f/25z9sC339YE5kutKMdIySi5lvpb+Qo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTinycxFpscdxS+C57=QhPjbuP184CQ@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwdDGUbuFlmFXd3r0+OcSs5LAcQyQ==
Thread-topic: [Xen-devel] [PATCH] mem_event: Allow memory access listener to perform single step execution
User-agent: Microsoft-Entourage/12.29.0.110113
I removed and unrelated and pointless change that broke the x86_32 build, as
c/s 23435. If that change is okay for you, I could backport the combination
of 23434+23435 to 4.1.1.

 -- Keir

On 27/05/2011 17:36, "Aravindh Puthiyaparambil" <aravindh@xxxxxxxxxxxx>
wrote:

> Can this be included in xen-4.1-testing.hg too so that it could make the Xen
> 4.1.1 cut?
> 
> Thanks,
> Aravindh
> 
> On May 27, 2011 1:39 AM, "Tim Deegan" <Tim.Deegan@xxxxxxxxxx> wrote:
>> At 04:39 +0100 on 27 May (1306471145), Aravindh Puthiyaparambil wrote:
>>> mem_event: Allow memory access listener to perform single step execution.
>>> Add a new memory event that handles single step. This allows the memory
>>> access listener to handle instructions that modify data within the execution
>>> page.
>>> This can be enabled in the listener by doing:
>>> xc_set_hvm_param(xch, domain_id, HVM_PARAM_MEMORY_EVENT_SINGLE_STEP,
>>> HVMPME_mode_sync)
>>> 
>>> Now the listener can start single stepping by:
>>> xc_domain_debug_control(xch, domain_id, XEN_DOMCTL_DEBUG_OP_SINGLE_STEP_ON,
>>> vcpu_id)
>>> 
>>> And stop single stepping by:
>>> xc_domain_debug_control(xch, domain_id, XEN_DOMCTL_DEBUG_OP_SINGLE_STEP_OFF,
>>> vcpu_id)
>>> 
>>> Signed-off-by: Aravindh Puthiyaparambil <aravindh@xxxxxxxxxxxx>
>> 
>> Acked-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
>> 
>> -- 
>> Tim Deegan <Tim.Deegan@xxxxxxxxxx>
>> Principal Software Engineer, Xen Platform Team
>> Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel