From: Christoffer Dall <christoffer.dall@linaro.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: marc.zyngier@arm.com, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] arm{,64}/kvm: excise redundant cache maintenance
Date: Thu, 1 Sep 2016 13:15:45 +0200 [thread overview]
Message-ID: <20160901111545.GC10162@cbox> (raw)
In-Reply-To: <20160830180020.GB19315@leverpostej>
On Tue, Aug 30, 2016 at 07:00:20PM +0100, Mark Rutland wrote:
> On Tue, Aug 30, 2016 at 05:05:54PM +0100, Mark Rutland wrote:
> > As noted in a jailhouse thread a short while ago [1,2], the presence of the
> > virtualization extensions implies that page table walks are coherent, and do
> > not require that updates are cleaned to the PoU.
> >
> > These patches remove the redundant maintenance and related infrastructure.
> >
> > As I do not have a suitably configured ARMv7 board, I have not been able to
> > test the patches myself, and any testing would be appreciated.
>
> Having been lent a TC2 booting in Hyp mode, I've now given this a spin
> with a few VMs, which I left running hackbench to fault in guest memory.
>
> All of that ran happily.
>
I've tested this on TC2 and CubieTruck as well, no problems as far as I
can see.
Applied.
Thanks,
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm{,64}/kvm: excise redundant cache maintenance
Date: Thu, 1 Sep 2016 13:15:45 +0200 [thread overview]
Message-ID: <20160901111545.GC10162@cbox> (raw)
In-Reply-To: <20160830180020.GB19315@leverpostej>
On Tue, Aug 30, 2016 at 07:00:20PM +0100, Mark Rutland wrote:
> On Tue, Aug 30, 2016 at 05:05:54PM +0100, Mark Rutland wrote:
> > As noted in a jailhouse thread a short while ago [1,2], the presence of the
> > virtualization extensions implies that page table walks are coherent, and do
> > not require that updates are cleaned to the PoU.
> >
> > These patches remove the redundant maintenance and related infrastructure.
> >
> > As I do not have a suitably configured ARMv7 board, I have not been able to
> > test the patches myself, and any testing would be appreciated.
>
> Having been lent a TC2 booting in Hyp mode, I've now given this a spin
> with a few VMs, which I left running hackbench to fault in guest memory.
>
> All of that ran happily.
>
I've tested this on TC2 and CubieTruck as well, no problems as far as I
can see.
Applied.
Thanks,
-Christoffer
next prev parent reply other threads:[~2016-09-01 11:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 16:05 [PATCH 0/2] arm{,64}/kvm: excise redundant cache maintenance Mark Rutland
2016-08-30 16:05 ` Mark Rutland
2016-08-30 16:05 ` [PATCH 1/2] arm/kvm: " Mark Rutland
2016-08-30 16:05 ` Mark Rutland
2016-08-30 16:05 ` [PATCH 2/2] arm64/kvm: remove unused stub functions Mark Rutland
2016-08-30 16:05 ` Mark Rutland
2016-08-30 18:00 ` [PATCH 0/2] arm{,64}/kvm: excise redundant cache maintenance Mark Rutland
2016-08-30 18:00 ` Mark Rutland
2016-09-01 11:15 ` Christoffer Dall [this message]
2016-09-01 11:15 ` 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=20160901111545.GC10162@cbox \
--to=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.