From: Jike Song <jike.song@intel.com>
To: Neo Jia <cjia@nvidia.com>
Cc: pbonzini@redhat.com, rkrcmar@redhat.com, kvm@vger.kernel.org,
alex.williamson@redhat.com, kevin.tian@intel.com,
kwankhede@nvidia.com
Subject: Re: [PATCH 0/2] extend page_track for external usage
Date: Wed, 26 Oct 2016 10:18:56 +0800 [thread overview]
Message-ID: <58101290.7070802@intel.com> (raw)
In-Reply-To: <20161025164224.GA27343@nvidia.com>
On 10/26/2016 12:42 AM, Neo Jia wrote:
> On Tue, Oct 25, 2016 at 03:50:41PM +0800, Jike Song wrote:
>> page_track is currently used only by KVM internally to protect guest
>> page tables. To be used by external user like KVMGT, the callbacks
>> should carry more information other than KVM/VCPU, and the symbols
>> should be exported.
>>
>> Jike Song (2):
>> kvm/page_track: call notifiers with kvm_page_track_notifier_node
>> kvm/page_track: export symbols for external usage
>>
>> arch/x86/include/asm/kvm_page_track.h | 7 +++++--
>> arch/x86/kvm/mmu.c | 6 ++++--
>> arch/x86/kvm/page_track.c | 8 ++++++--
>> 3 files changed, 15 insertions(+), 6 deletions(-)
>
> Hi Jike,
>
> What is the plan of providing this functionality to the VFIO based mediated
> vendor driver?
>
> JFYI, this is a useful feature that NVIDIA vGPU also needs.
Hi Neo,
The page_track implementation is almost ready for external usage, my
changes here are quite trivial. I guess the external user like your
vendor driver can call them directly.
BTW, do you also have to shadow the device page-tables? Per my previous
understanding you don't have to.
--
Thanks,
Jike
next prev parent reply other threads:[~2016-10-26 2:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 7:50 [PATCH 0/2] extend page_track for external usage Jike Song
2016-10-25 7:50 ` [PATCH 1/2] kvm/page_track: call notifiers with kvm_page_track_notifier_node Jike Song
2016-10-25 7:50 ` [PATCH 2/2] kvm/page_track: export symbols for external usage Jike Song
2016-10-25 15:59 ` [PATCH 0/2] extend page_track " Jike Song
2016-10-25 16:42 ` Neo Jia
2016-10-26 2:18 ` Jike Song [this message]
2016-10-26 7:39 ` Neo Jia
2016-10-26 7:44 ` Paolo Bonzini
2016-10-26 7:57 ` Tian, Kevin
2016-10-26 8:03 ` Neo Jia
2016-10-26 7:48 ` Paolo Bonzini
2016-11-04 5:47 ` Jike Song
2016-11-04 10:02 ` Paolo Bonzini
2016-11-04 10:29 ` Zhenyu Wang
2016-11-04 11:22 ` Paolo Bonzini
2016-11-05 13:22 ` Zhenyu Wang
2016-11-06 13:22 ` Jike Song
2016-11-07 9:17 ` Daniel Vetter
2016-11-09 2:03 ` Zhenyu Wang
2016-11-09 14:23 ` Paolo Bonzini
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=58101290.7070802@intel.com \
--to=jike.song@intel.com \
--cc=alex.williamson@redhat.com \
--cc=cjia@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.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.