From: Gleb Natapov <gleb@redhat.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: fix async page fault working for readonly mapping
Date: Mon, 21 May 2012 11:08:56 +0300 [thread overview]
Message-ID: <20120521080856.GS10209@redhat.com> (raw)
In-Reply-To: <4FB9E499.2010505@linux.vnet.ibm.com>
On Mon, May 21, 2012 at 02:45:45PM +0800, Xiao Guangrong wrote:
> If we map a readonly memory space from host to guest and the page is
> not currently mapped in the host, we will get a fault-pfn and async
> is not allowed, then the vm will crash
>
Why would we want to map a readonly memory space from host to guest?
We may want to do it to support memory semantics on read and mmio on
write, but do not right now unless something changed while I was not
looking.
> The reason is only writable vma can be allowed to be async in current
> code
>
> Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
> ---
> virt/kvm/kvm_main.c | 19 +++++++++++++++++--
> 1 files changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 6bd34a6..b6c8962 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -1052,6 +1052,21 @@ static inline int check_user_page_hwpoison(unsigned long addr)
> return rc == -EHWPOISON;
> }
>
> +static bool vma_is_avalid(struct vm_area_struct *vma, bool write_fault)
> +{
> + if (write_fault) {
> + if (unlikely(!(vma->vm_flags & VM_WRITE)))
> + return false;
> +
> + return true;
> + }
> +
> + if (unlikely(!(vma->vm_flags & (VM_READ | VM_EXEC | VM_WRITE))))
> + return false;
> +
> + return true;
> +}
> +
> static pfn_t hva_to_pfn(struct kvm *kvm, unsigned long addr, bool atomic,
> bool *async, bool write_fault, bool *writable)
> {
> @@ -1075,7 +1090,6 @@ static pfn_t hva_to_pfn(struct kvm *kvm, unsigned long addr, bool atomic,
>
> if (writable)
> *writable = write_fault;
> -
> if (async) {
> down_read(¤t->mm->mmap_sem);
> npages = get_user_page_nowait(current, current->mm,
> @@ -1122,8 +1136,9 @@ static pfn_t hva_to_pfn(struct kvm *kvm, unsigned long addr, bool atomic,
> vma->vm_pgoff;
> BUG_ON(!kvm_is_mmio_pfn(pfn));
> } else {
> - if (async && (vma->vm_flags & VM_WRITE))
> + if (async && vma_is_avalid(vma, write_fault))
> *async = true;
> +
> pfn = get_fault_pfn();
> }
> up_read(¤t->mm->mmap_sem);
> --
> 1.7.7.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Gleb.
next prev parent reply other threads:[~2012-05-21 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 6:45 [PATCH] KVM: fix async page fault working for readonly mapping Xiao Guangrong
2012-05-21 8:08 ` Gleb Natapov [this message]
2012-05-21 8:15 ` Xiao Guangrong
2012-05-21 19:30 ` Marcelo Tosatti
2012-05-22 5:31 ` Gleb Natapov
2012-05-22 14:27 ` Avi Kivity
2012-05-23 3:09 ` Xiao Guangrong
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=20120521080856.GS10209@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@linux.vnet.ibm.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).