On 5 November 2015 at 06:50, Pavel Fedin
> You know, since we are talking about this... This definitely
> has something to do with the reset, and... Looks like nobody
> resets vGIC/vTimer, unless the userland does it explicitly by
> resetting every register by hand.
This is how KVM in-kernel de
Hello!
> Actually, I seem to have been just incredibly unlucky with my test
> cycles, because I eventually reproduced the bug without your patches.
Or lucky, without "un" :)
> I'm going to take this version of the series because that's what I
> reviewed and tested.
It's OK, as i wrote, v5 is
On Tue, Nov 03, 2015 at 12:44:54PM +0300, Pavel Fedin wrote:
> Hello!
>
> > By this time i'll make a very minimal version of patch 0001, for you to
> > test it. If we have
> > problems with current 0001, which we
> > cannot solve quickly, we could stick to that version then, which will
> > pro
Hello!
> By this time i'll make a very minimal version of patch 0001, for you to test
> it. If we have
> problems with current 0001, which we
> cannot solve quickly, we could stick to that version then, which will provide
> the necessary
> changes to plug in LPIs, yet with
> minimal changes (i
Hello!
> I ran this through my test scripts and I'm now quite sure that there's
> some breakage in here.
>
> One of my tests is running two VMs in parallel, each booting up, running
> hackbench, and then doing reboot (from within the guest), and just
> repeating like that.
>
> I've run your pat
On Tue, Oct 27, 2015 at 11:37:28AM +0300, Pavel Fedin wrote:
> Current KVM code has lots of old redundancies, which can be cleaned up.
> This patchset is actually a better alternative to
> http://www.spinics.net/lists/arm-kernel/msg430726.html, which allows to
> keep piggy-backed LRs. The idea is b