linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/9] arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn()
Date: Tue, 9 Dec 2014 13:38:14 +0100	[thread overview]
Message-ID: <20141209123814.GA15880@cbox> (raw)
In-Reply-To: <CAKv+Gu8Y+gQmDBGCwiLYGpTtE9MnNpu6YnNJDEJjBoi+XBxV2g@mail.gmail.com>

On Tue, Dec 09, 2014 at 01:29:52PM +0100, Ard Biesheuvel wrote:
> On 9 December 2014 at 12:26, Christoffer Dall
> <christoffer.dall@linaro.org> wrote:
> > From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >
> > 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>
> > Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> 
> As I mentioned last week, this patch (and the next one) are already in
> 3.18 so unless there is some policy I am unaware of, these do not have
> to be submitted again.
> 
They're in kvmarm/next, which is a stable branch (doesn't rebase) so our
only choice would be to revert this commit specifically in kvmarm/next
before sending the pull request.  Since that would be more confusing
than help anything, and Paolo said to just include the duplicate commit
in the pull request, here it is.

As we can see in linux-next, it's not really a problem.

-Christoffer

  reply	other threads:[~2014-12-09 12:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 11:25 [GIT PULL 0/9] KVM/ARM Changes for v3.19 Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 1/9] KVM: ARM: VGIC: Optimize the vGIC vgic_update_irq_pending function Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 2/9] arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn() Christoffer Dall
2014-12-09 12:29   ` Ard Biesheuvel
2014-12-09 12:38     ` Christoffer Dall [this message]
2014-12-09 12:38       ` Ard Biesheuvel
2014-12-09 11:26 ` [GIT PULL 3/9] kvm: fix kvm_is_mmio_pfn() and rename to kvm_is_reserved_pfn() Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 4/9] kvm: add a memslot flag for incoherent memory regions Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 5/9] arm, arm64: KVM: allow forced dcache flush on page faults Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 6/9] arm, arm64: KVM: handle potential incoherency of readonly memslots Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 7/9] arm/arm64: KVM: avoid unnecessary guest register mangling on MMIO read Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 8/9] arm/arm64: vgic: Remove unreachable irq_clear_pending Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 9/9] arm/arm64: KVM: vgic: kick the specific vcpu instead of iterating through all Christoffer Dall
2014-12-09 19:39 ` [GIT PULL 0/9] KVM/ARM Changes for v3.19 Paolo Bonzini
2014-12-11  9:47   ` Christoffer Dall
2014-12-11 11:54     ` Paolo Bonzini
2014-12-11 12:02       ` Christoffer Dall
2014-12-11 11:52 ` Paolo Bonzini
2014-12-11 11:59   ` Christoffer Dall
2014-12-11 12:04     ` Paolo Bonzini

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=20141209123814.GA15880@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).