From: Kevin Hilman <khilman@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Possible regression in next-20150323 due to "ARM, arm64: kvm: get rid of the bounce page"
Date: Wed, 01 Apr 2015 18:12:10 +0000 [thread overview]
Message-ID: <7hmw2r67lx.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150401085832.GA1552@arm.com> (Will Deacon's message of "Wed, 1 Apr 2015 09:58:32 +0100")
Hi Will,
Will Deacon <will.deacon@arm.com> writes:
[...]
>> >
>> > Thanks for testing this and sorry for the continued breakage. Which
>> > toolchain did you say you were using? Ard has some more patches trying to
>> > fix this, but none of our toolchains seem to tickle the issue.
>>
>> I've also tested on the default ARM toolchains available with ubuntu[1]
>>
>> Are there any updates on this issue?
>
> It's been fixed since the end of last week!
>
> (see ARM: kvm: round HYP section to page size instead of log2 upper bound)
>
> This was confirmed by both my testing and also Simon Horman, who reported
> the initial breakage.
>
>> It ha broken most of the ARM defconfigs in linux-next[2], and since it's
>> been broken for a week now, it is masking other types of issues that we
>> can normally find via automated boot testing.
>
> If you're referring to failures such as:
>
> http://storage.kernelci.org/next/next-20150331/arm-axm55xx_defconfig/build.log
Yes, that's the one I'm trying to track down.
> Then that's not coming from the arm64 tree, and is a completely separate
> issue from the one originally reported in this thread.
Ugh, womehow I got wires crossed and thought they were related problems.
Looks like Geert now has a proposed fix for the issue I'm tracking.
Sorry for the noise,
Kevin
prev parent reply other threads:[~2015-04-01 18:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 0:45 Possible regression in next-20150323 due to "ARM, arm64: kvm: get rid of the bounce page" Simon Horman
2015-03-24 0:52 ` Tyler Baker
2015-03-24 0:53 ` Tyler Baker
2015-03-24 8:31 ` Ard Biesheuvel
2015-03-24 16:13 ` Nishanth Menon
2015-03-26 0:39 ` Simon Horman
2015-03-26 13:36 ` Will Deacon
2015-03-26 15:29 ` Tyler Baker
2015-03-27 0:25 ` Simon Horman
2015-03-27 10:06 ` Will Deacon
2015-03-27 11:55 ` Simon Horman
2015-03-27 15:18 ` Tyler Baker
[not found] ` <7hbnj99epe.fsf@deeprootsystems.com>
2015-03-31 21:39 ` Ard Biesheuvel
2015-03-31 22:10 ` Kevin Hilman
2015-04-01 9:37 ` [PATCH] mm/migrate: Mark unmap_and_move() "noinline" to avoid ICE in gcc 4.7.3 (was: Re: Possible re Geert Uytterhoeven
2015-04-01 9:47 ` [PATCH] mm/migrate: Mark unmap_and_move() "noinline" to avoid ICE in gcc 4.7.3 Marc Zyngier
2015-04-01 19:40 ` Andrew Morton
2015-04-01 21:54 ` Kevin Hilman
2015-04-01 21:59 ` Russell King - ARM Linux
2015-04-02 7:17 ` Geert Uytterhoeven
2015-04-02 19:12 ` Lina Iyer
2015-04-02 21:12 ` Kevin Hilman
2015-04-02 21:53 ` Lina Iyer
2015-04-07 17:57 ` Kevin Hilman
2015-04-07 20:17 ` Andrew Morton
2015-04-07 22:41 ` Kevin Hilman
2015-04-07 22:53 ` Andrew Morton
2015-04-07 23:27 ` Kevin Hilman
2015-04-07 23:36 ` Andrew Morton
2015-04-08 0:15 ` Kevin Hilman
2015-04-01 19:27 ` Kevin Hilman
2015-04-01 8:58 ` Possible regression in next-20150323 due to "ARM, arm64: kvm: get rid of the bounce page" Will Deacon
2015-04-01 13:54 ` Nishanth Menon
2015-04-01 18:12 ` Kevin Hilman [this message]
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=7hmw2r67lx.fsf@deeprootsystems.com \
--to=khilman@kernel.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).