From: Paolo Bonzini <pbonzini@redhat.com>
To: KarimAllah Ahmed <karahmed@amazon.de>, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kvm: Map PFN-type memory regions as writable (if possible)
Date: Thu, 18 Jan 2018 09:36:16 +0100 [thread overview]
Message-ID: <091cebf2-4403-93b9-6eb2-2bc73a4c96af@redhat.com> (raw)
In-Reply-To: <1516213136-12883-1-git-send-email-karahmed@amazon.de>
On 17/01/2018 19:18, KarimAllah Ahmed wrote:
> For EPT-violations that are triggered by a read, the pages are also mapped with
> write permissions (if their memory region is also writable). That would avoid
> getting yet another fault on the same page when a write occurs.
>
> This optimization only happens when you have a "struct page" backing the memory
> region. So also enable it for memory regions that do not have a "struct page".
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Cc: kvm@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: KarimAllah Ahmed <karahmed@amazon.de>
>
> ---
> v2:
> - Move setting writable to hva_to_pfn_remapped
> - Extend hva_to_pfn_remapped interface to accept writable as a parameter
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> virt/kvm/kvm_main.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 97da45e..88702d5 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -1438,7 +1438,8 @@ static bool vma_is_valid(struct vm_area_struct *vma, bool write_fault)
>
> static int hva_to_pfn_remapped(struct vm_area_struct *vma,
> unsigned long addr, bool *async,
> - bool write_fault, kvm_pfn_t *p_pfn)
> + bool write_fault, bool *writable,
> + kvm_pfn_t *p_pfn)
> {
> unsigned long pfn;
> int r;
> @@ -1464,6 +1465,8 @@ static int hva_to_pfn_remapped(struct vm_area_struct *vma,
>
> }
>
> + if (writable)
> + *writable = true;
>
> /*
> * Get a reference here because callers of *hva_to_pfn* and
> @@ -1529,7 +1532,7 @@ static kvm_pfn_t hva_to_pfn(unsigned long addr, bool atomic, bool *async,
> if (vma == NULL)
> pfn = KVM_PFN_ERR_FAULT;
> else if (vma->vm_flags & (VM_IO | VM_PFNMAP)) {
> - r = hva_to_pfn_remapped(vma, addr, async, write_fault, &pfn);
> + r = hva_to_pfn_remapped(vma, addr, async, write_fault, writable, &pfn);
> if (r == -EAGAIN)
> goto retry;
> if (r < 0)
>
prev parent reply other threads:[~2018-01-18 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:26 [PATCH] kvm: Map PFN-type memory regions as writable (if possible) KarimAllah Ahmed
2018-01-17 17:56 ` Paolo Bonzini
2018-01-17 18:18 ` [PATCH v2] " KarimAllah Ahmed
2018-01-18 8:36 ` Paolo Bonzini [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=091cebf2-4403-93b9-6eb2-2bc73a4c96af@redhat.com \
--to=pbonzini@redhat.com \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).