> The best thing to do is probably to wait for for kvm_vcpu_map() to be
> eliminated,
> as described in the changelogs for commits:
>
> 357a18ad230f ("KVM: Kill kvm_map_gfn() / kvm_unmap_gfn() and
> gfn_to_pfn_cache")
> 7e2175ebd695 ("KVM: x86: Fix recording of guest steal time / preempted
>
> > These are the type of pages which KVM is currently rejecting. Is this
> > something that KVM can support?
>
> I'm not opposed to it. My complaint is that this series is incomplete in
> that it
> allows mapping the memory into the guest, but doesn't support accessing the
> memory
> from KVM i
On Thu, Jan 6, 2022 at 4:19 AM Sean Christopherson wrote:
>
> On Wed, Jan 05, 2022, Sean Christopherson wrote:
> > Ah, I got royally confused by ensure_pfn_ref()'s comment
> >
> > * Certain IO or PFNMAP mappings can be backed with valid
> > * struct pages, but be allocated without refcounting
On Fri, Dec 31, 2021 at 4:22 AM Sean Christopherson wrote:
>
> On Mon, Nov 29, 2021, David Stevens wrote:
> > From: David Stevens
> >
> > Remove two warnings that require ref counts for pages to be non-zero, as
> > mapped pfns from follow_pfn may not have an initialized ref count.
> >
> > Signed-
From: David Stevens
Remove two warnings that require ref counts for pages to be non-zero, as
mapped pfns from follow_pfn may not have an initialized ref count.
Signed-off-by: David Stevens
---
arch/x86/kvm/mmu/mmu.c | 7 ---
virt/kvm/kvm_main.c| 2 +-
2 files changed, 1 insertion(+), 8
