From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Tim Deegan <tim@xen.org>
Cc: kevin.tian@intel.com, keir@xen.org, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, jun.nakajima@intel.com,
ian.jackson@eu.citrix.com, eddie.dong@intel.com,
jbeulich@suse.com, andrew.cooper3@citrix.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH V10 for-4.5 0/4] Basic guest memory introspection support
Date: Thu, 18 Sep 2014 14:20:57 +0300 [thread overview]
Message-ID: <541AC019.60100@bitdefender.com> (raw)
In-Reply-To: <20140918110822.GC64996@deinos.phlegethon.org>
On 09/18/2014 02:08 PM, Tim Deegan wrote:
> At 11:24 +0300 on 18 Sep (1411035862), Razvan Cojocaru wrote:
>> We need to be able to detect rootkits in HVM guests, in a way that
>> allows an application that runs in dom0 (or a similarly privileged
>> domain) to control what the guest is allowed to do once a threat is
>> detected. This has been done over the mem_event mechanism.
>>
>> Here is a summary of the series:
>>
>> a 1/4 xen: Emulate with no writes
>> a 2/4 xen: Optimize introspection access to guest state
>> A 3/4 xen, libxc: Force-enable relevant MSR events
>> - 4/4 xen: Handle resumed instruction based on previous mem_event reply
>
> For the x86/mm and mem_event parts,
>
> Acked-by: Tim Deegan <tim@xen.org>
Thanks!
Regards,
Razvan Cojocaru
prev parent reply other threads:[~2014-09-18 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 8:24 [PATCH V10 for-4.5 0/4] Basic guest memory introspection support Razvan Cojocaru
2014-09-18 8:24 ` [PATCH V10 for-4.5 1/4] xen: Emulate with no writes Razvan Cojocaru
2014-09-18 8:24 ` [PATCH V10 for-4.5 2/4] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-09-18 8:24 ` [PATCH V10 for-4.5 3/4] xen, libxc: Force-enable relevant MSR events Razvan Cojocaru
2014-09-18 14:51 ` Tamas K Lengyel
2014-09-18 15:18 ` Razvan Cojocaru
2014-09-18 17:03 ` Tamas K Lengyel
2014-09-18 8:24 ` [PATCH V10 for-4.5 4/4] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-09-18 11:08 ` [PATCH V10 for-4.5 0/4] Basic guest memory introspection support Tim Deegan
2014-09-18 11:20 ` Razvan Cojocaru [this message]
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=541AC019.60100@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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.