All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Adalbert Lazăr" <alazar@bitdefender.com>, linux-mm@kvack.org
Cc: kvm@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Mihai Donțu" <mdontu@bitdefender.com>
Subject: Re: [RFC PATCH v5 00/20] VM introspection
Date: Fri, 21 Dec 2018 10:39:17 -0500	[thread overview]
Message-ID: <20181221153917.GA8195@char.us.oracle.com> (raw)
In-Reply-To: <20181220182850.4579-1-alazar@bitdefender.com>

On Thu, Dec 20, 2018 at 08:28:30PM +0200, Adalbert Lazăr wrote:
> This patch series proposes a VM introspection subsystem for KVM (KVMi).
> 
> The previous RFC can be read here: https://marc.info/?l=kvm&m=151362403331566
> 
> This iteration brings, mostly:
>   - an improved remote mapping (moved to the mm/ tree)
>   - single-step support for #PF events and as an workaround to unimplemented
>     instructions from the x86 emulator that may need to be handled on EPT
>     violations VMEXITS
>   - a new ioctl to allow the introspection tool to remove its hooks from
>     guest before it is suspended or live migrated

.. No mention of the libvmi tool - are you going to provide the functionality
in there as well to use these new ioctls? Would it make sense to CC the libvmi
community as well to get their input?

>   - more bugfixes and a lot of stability
> 
> Still not implemented yet (even if some are documented) are virtualized
> exceptions, EPT views and SPP (Sub Page Protection).
> 
> We're still looking forward to add kvm unit tests for this VM
> introspection system now that we've integrated it in our products and
> in our internal tests framework.

..snip..> 

>  mm/Kconfig                               |    9 +
>  mm/Makefile                              |    1 +
>  mm/gup.c                                 |    1 +
>  mm/huge_memory.c                         |    1 +
>  mm/internal.h                            |    5 -
>  mm/mempolicy.c                           |    1 +
>  mm/mmap.c                                |    1 +
>  mm/mmu_notifier.c                        |    1 +
>  mm/pgtable-generic.c                     |    1 +
>  mm/remote_mapping.c                      | 1438 ++++++++++++++
>  mm/rmap.c                                |   39 +-
>  mm/swapfile.c                            |    1 +

Please make sure to CC linux-mm@kvack.org when posting this.

In the meantime for folks on linux-mm, pls see https://www.spinics.net/lists/kvm/msg179441.html

       reply	other threads:[~2018-12-21 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181220182850.4579-1-alazar@bitdefender.com>
2018-12-21 15:39 ` Konrad Rzeszutek Wilk [this message]
2018-12-21 16:51   ` [RFC PATCH v5 00/20] VM introspection Mihai Donțu

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=20181221153917.GA8195@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=alazar@bitdefender.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mdontu@bitdefender.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    /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.