[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140107185040.GB4223@kroah.com>
Date: Tue, 7 Jan 2014 10:50:40 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Mark Rutland <mark.rutland@....com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
Catalin Marinas <Catalin.Marinas@....com>,
Marc Zyngier <Marc.Zyngier@....com>,
Santosh Shilimkar <santosh.shilimkar@...com>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
Mark Brown <broonie@...nel.org>,
John Garry <john.garry@...adcom.com>
Subject: Re: [PATCH 3.10 126/129] clocksource: arch_timer: use virtual
counters
On Tue, Jan 07, 2014 at 10:09:50AM +0000, Mark Rutland wrote:
> Hi Greg,
>
> On Mon, Jan 06, 2014 at 10:39:15PM +0000, Greg Kroah-Hartman wrote:
> > 3.10-stable review patch. If anyone has any objections, please let me know.
>
> This patch alone may break ARM systems booted at hyp mode or when KVM is
> in use, causing CPUs to have different views of time or for a given
> CPU's view of time to jump backwards.
>
> The following two commits in mainline fix those two problems by ensuring
> all CPUs have the same virtual timer offset (zero), and maintaining it
> across KVM world switches. On arm64 the requisite CNTVOFF zeroing is
> already present in linux-3.10.y.
>
> 0af0b189abf7 (ARM: hyp: initialize CNTVOFF to zero)
> f793c23ebbe5 (ARM: KVM: arch_timers: zero CNTVOFF upon return to host)
Thanks, I've now queued up both of these patches as well. With that, we
should be ok, right?
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists