[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <61b16167-33cf-f435-6a9b-c20ab299e8d2@redhat.com>
Date: Wed, 25 Jul 2018 11:36:23 +0200
From: David Hildenbrand <david@...hat.com>
To: Ahmed Abd El Mawgood <ahmedsoliman0x666@...il.com>, kvm@...r.kernel.org,
Kernel Hardening <kernel-hardening@...ts.openwall.com>,
virtualization@...ts.linux-foundation.org, linux-doc@...r.kernel.org,
x86@...nel.org, xen-devel@...ts.xensource.com
Cc: Paolo Bonzini <pbonzini@...hat.com>, rkrcmar@...hat.com,
nathan Corbet <corbet@....net>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, hpa@...or.com,
Kees Cook <keescook@...omium.org>, Ard Biesheuvel
<ard.biesheuvel@...aro.org>, Boris Lukashev <blukashev@...pervictus.com>,
David Vrabel <david.vrabel@...anix.com>, nigel.edwards@....com,
Rik van Riel <riel@...riel.com>
Subject: Re: [PATCH RFC V4 3/3] KVM: X86: Adding skeleton for Memory ROE
> if (kvm_x86_ops->slot_disable_log_dirty)
> kvm_x86_ops->slot_disable_log_dirty(kvm, new);
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> index 4ee7bc548a83..82c5780e11d9 100644
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -297,6 +297,9 @@ static inline int kvm_vcpu_exiting_guest_mode(struct kvm_vcpu *vcpu)
> struct kvm_memory_slot {
> gfn_t base_gfn;
> unsigned long npages;
> +#ifdef CONFIG_KVM_MROE
> + unsigned long *mroe_bitmap;
> +#endif
Yet another problematic bitmap when it comes to splitting/resizing
memory slots atomically :(
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
