From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH for-4.5 v11 0/9] Mem_event and mem_access for ARM Date: Mon, 29 Sep 2014 16:21:36 +0100 Message-ID: <1412004096.3801.28.camel@citrix.com> References: <1411990609-22374-1-git-send-email-tklengyel@sec.in.tum.de> <1411997842.3801.16.camel@citrix.com> <1412003230.3801.26.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tamas K Lengyel Cc: wei.liu2@citrix.com, Tim Deegan , "xen-devel@lists.xen.org" , Stefano Stabellini , Daniel De Graaf List-Id: xen-devel@lists.xenproject.org On Mon, 2014-09-29 at 17:17 +0200, Tamas K Lengyel wrote: > > For example I think they would would have pretty clearly shown > poor > performance due to the copy to/from user changes in your > previous > iteration. > > Ian. > > > You are probably right, but aren't the copy to/from helpers only used > if the guest is issuing hypercalls? I mean, what would the hypervisor > copy in/out of the guest during kernbench running in the guest? That > doesn't really sound right to me. Guests (and dom0 issue hypercalls as part of the PV ring protocols (kicking evtchns, mapping and unmapping grant references, etc) and for a variety of other things while they are running workloads. For almost all of those operations some sort of argument struct normally needs to be copied in/out (often both) of guest memory. Ian.