public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: magnus.karlsson@avagotech.com, pbonzini@redhat.com,
	m.smarduch@samsung.com, kvmarm@lists.cs.columbia.edu,
	kvm@vger.kernel.org, marc.zyngier@arm.com
Subject: Re: [PATCH 1/2] arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn()
Date: Mon, 10 Nov 2014 11:57:04 +0100	[thread overview]
Message-ID: <20141110105704.GB7544@cbox> (raw)
In-Reply-To: <1415608436-5127-1-git-send-email-ard.biesheuvel@linaro.org>

On Mon, Nov 10, 2014 at 09:33:55AM +0100, Ard Biesheuvel wrote:
> Instead of using kvm_is_mmio_pfn() to decide whether a host region
> should be stage 2 mapped with device attributes, add a new static
> function kvm_is_device_pfn() that disregards RAM pages with the
> reserved bit set, as those should usually not be mapped as device
> memory.
> 
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
>  arch/arm/kvm/mmu.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/kvm/mmu.c b/arch/arm/kvm/mmu.c
> index 57a403a5c22b..b007438242e2 100644
> --- a/arch/arm/kvm/mmu.c
> +++ b/arch/arm/kvm/mmu.c
> @@ -834,6 +834,11 @@ static bool kvm_is_write_fault(struct kvm_vcpu *vcpu)
>  	return kvm_vcpu_dabt_iswrite(vcpu);
>  }
>  
> +static bool kvm_is_device_pfn(unsigned long pfn)
> +{
> +	return !pfn_valid(pfn);
> +}

So this works for Magnus' use case, because a device tree memreserve
results in reserved, but valid, existing pages being backed by a struct
page?

> +
>  static int user_mem_abort(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa,
>  			  struct kvm_memory_slot *memslot, unsigned long hva,
>  			  unsigned long fault_status)
> @@ -904,7 +909,7 @@ static int user_mem_abort(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa,
>  	if (is_error_pfn(pfn))
>  		return -EFAULT;
>  
> -	if (kvm_is_mmio_pfn(pfn))
> +	if (kvm_is_device_pfn(pfn))
>  		mem_type = PAGE_S2_DEVICE;
>  
>  	spin_lock(&kvm->mmu_lock);
> -- 
> 1.8.3.2
> 

If my understanding above is correct, then:

Acked-by: Christoffer Dall <christoffer.dall@linaro.org>

  parent reply	other threads:[~2014-11-10 10:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10  8:33 [PATCH 1/2] arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn() Ard Biesheuvel
2014-11-10  8:33 ` [PATCH 2/2] kvm: fix kvm_is_mmio_pfn() and rename to kvm_is_reserved_pfn() Ard Biesheuvel
2014-11-10 10:53   ` Christoffer Dall
2014-11-10 11:05     ` Ard Biesheuvel
2014-11-10 11:11       ` Christoffer Dall
2014-11-21 11:30   ` Ard Biesheuvel
2014-11-21 11:46   ` Christoffer Dall
2014-11-21 13:06     ` Paolo Bonzini
2014-11-21 13:18       ` Christoffer Dall
2014-11-21 18:37         ` Paolo Bonzini
2014-11-21 18:35   ` Paolo Bonzini
2014-11-22 10:16     ` Christoffer Dall
2014-11-10 10:57 ` Christoffer Dall [this message]
2014-11-10 11:15   ` [PATCH 1/2] arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn() Ard Biesheuvel
2014-11-21 11:24 ` Christoffer Dall
2014-12-01  9:16   ` Ard Biesheuvel
2014-12-01  9:54     ` Paolo Bonzini
2014-12-01 12:23       ` Christoffer Dall

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=20141110105704.GB7544@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=m.smarduch@samsung.com \
    --cc=magnus.karlsson@avagotech.com \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@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