From mboxrd@z Thu Jan 1 00:00:00 1970 From: Razvan Cojocaru Subject: Re: [PATCH RFC V3 4/5] xen, libxc: Request page fault injection via libxc Date: Thu, 24 Jul 2014 15:44:07 +0300 Message-ID: <53D0FF97.3030602@bitdefender.com> References: <1406118884-16628-1-git-send-email-rcojocaru@bitdefender.com> <1406118884-16628-4-git-send-email-rcojocaru@bitdefender.com> <53CFC1EB.8080308@bitdefender.com> <53CFD108.5020107@bitdefender.com> <53D01874.80109@bitdefender.com> <21456.65069.187119.457145@mariner.uk.xensource.com> <53D0FEE9.90205@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <53D0FEE9.90205@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 , Ian Jackson , Andrei LUTAS Cc: kevin.tian@intel.com, Ian Campbell , Stefano Stabellini , jun.nakajima@intel.com, Tamas Lengyel , eddie.dong@intel.com, "xen-devel@lists.xen.org" , Andres Lagar-Cavilla , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 07/24/2014 03:41 PM, Andrew Cooper wrote: > On 24/07/14 13:38, Ian Jackson wrote: >> Andrei LUTAS writes ("Re: [Xen-devel] [PATCH RFC V3 4/5] xen, libxc: Request page fault injection via libxc"): >>> The logic with the #PF injection goes like this: >> Sorry, I didn't see this message when I sent my last one asking about >> the motivation. >> >>> - The memory introspection engine wants to inspect (for whatever reason) a >>> virtual page X insidevirtual address space Y(inside user-mode, although >>> with proper knowledge about the guest kernel,one can also inject #PF >>> inside >>> kernel-mode on Windows - proper IRQL, working set trim inactive, etc.) >> I don't understand why this needs additional hypervisor code. Can >> this not be done by negotiating with the paging daemon ? >> >> Ian. > > The purpose of this is to play with the paging algorithm inside the > guest OS, which can only be done from outside by providing pagefaults > when considered safe to do so. > > This has nothing to do with xen-paging transparently playing with the > guest physical address space behind the guests back. Thanks, you beat me to it :) Razvan Cojocaru