From mboxrd@z Thu Jan 1 00:00:00 1970 From: Razvan Cojocaru Subject: Re: [PATCH RFC 5/9] xen: Support for VMCALL mem_events Date: Wed, 02 Jul 2014 18:59:38 +0300 Message-ID: <53B42C6A.4040900@bitdefender.com> References: <1404308041-15461-1-git-send-email-rcojocaru@bitdefender.com> <1404308041-15461-5-git-send-email-rcojocaru@bitdefender.com> <53B42B2A.4020907@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <53B42B2A.4020907@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper , xen-devel@lists.xen.org Cc: tim@xen.org List-Id: xen-devel@lists.xenproject.org On 07/02/2014 06:54 PM, Andrew Cooper wrote: > On 02/07/14 14:33, Razvan Cojocaru wrote: >> Added support for VMCALL events (the memory introspection library >> will have the guest trigger VMCALLs, which will then be sent along >> via the mem_event mechanism). >> >> Signed-off-by: Razvan Cojocaru > > Am I correct in concluding that this is an escape mechanism for > something inside the guest to trap to the toolstack userspace monitoring > the guest? Yes. Thanks, Razvan Cojocaru