From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Andrei LUTAS <vlutas@bitdefender.com>
Cc: kevin.tian@intel.com, Ian Campbell <Ian.Campbell@citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tamas Lengyel <tamas.lengyel@zentific.com>,
eddie.dong@intel.com,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>,
Andres Lagar-Cavilla <andres@lagarcavilla.org>,
jun.nakajima@intel.com
Subject: Re: [PATCH RFC V3 4/5] xen, libxc: Request page fault injection via libxc
Date: Thu, 24 Jul 2014 13:41:13 +0100 [thread overview]
Message-ID: <53D0FEE9.90205@citrix.com> (raw)
In-Reply-To: <21456.65069.187119.457145@mariner.uk.xensource.com>
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.
~Andrew
next prev parent reply other threads:[~2014-07-24 12:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 12:34 [PATCH RFC V3 1/5] xen: Emulate with no writes Razvan Cojocaru
2014-07-23 12:34 ` [PATCH RFC V3 2/5] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-07-24 15:07 ` Jan Beulich
2014-07-23 12:34 ` [PATCH RFC V3 3/5] xen: Force-enable relevant MSR events; optimize the number of sent MSR events Razvan Cojocaru
2014-07-24 15:14 ` Jan Beulich
2014-07-24 15:56 ` Razvan Cojocaru
2014-07-23 12:34 ` [PATCH RFC V3 4/5] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-07-23 13:40 ` Tamas Lengyel
2014-07-23 14:08 ` Razvan Cojocaru
2014-07-23 14:27 ` Tamas Lengyel
2014-07-23 15:13 ` Razvan Cojocaru
2014-07-23 20:17 ` Andrei LUTAS
2014-07-24 12:38 ` Ian Jackson
2014-07-24 12:41 ` Andrew Cooper [this message]
2014-07-24 12:44 ` Razvan Cojocaru
2014-07-24 12:33 ` Ian Jackson
2014-07-24 15:27 ` Jan Beulich
2014-07-24 16:18 ` Razvan Cojocaru
2014-07-25 7:50 ` Jan Beulich
2014-07-23 12:34 ` [PATCH RFC V3 5/5] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-07-24 15:42 ` Jan Beulich
2014-07-24 16:29 ` Razvan Cojocaru
2014-07-25 7:52 ` Jan Beulich
2014-07-24 11:20 ` [PATCH RFC V3 1/5] xen: Emulate with no writes Tim Deegan
2014-07-24 11:40 ` Razvan Cojocaru
2014-07-25 13:52 ` Razvan Cojocaru
2014-07-25 14:07 ` Jan Beulich
2014-07-24 12:32 ` Ian Jackson
2014-07-24 12:36 ` Razvan Cojocaru
2014-07-24 12:37 ` Razvan Cojocaru
2014-07-24 17:25 ` Tian, Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53D0FEE9.90205@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andres@lagarcavilla.org \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tamas.lengyel@zentific.com \
--cc=vlutas@bitdefender.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.