From: Julien Grall <julien.grall@linaro.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xensource.com
Cc: julien.grall@citrix.com, Ian.Campbell@citrix.com,
andrii.tseglytskyi@globallogic.com
Subject: Re: [PATCH v2 for-4.5] xen/arm: clear UIE on hypervisor entry
Date: Thu, 20 Nov 2014 11:06:24 +0000 [thread overview]
Message-ID: <546DCB30.6040400@linaro.org> (raw)
In-Reply-To: <546DCA3F.2030508@linaro.org>
On 11/20/2014 11:02 AM, Julien Grall wrote:
> Hi Stefano,
>
> On 11/20/2014 10:53 AM, Stefano Stabellini wrote:
>> UIE being set can cause maintenance interrupts to occur when Xen writes
>> to one or more LR registers. The effect is a busy loop around the
>> interrupt handler in Xen
>> (http://marc.info/?l=xen-devel&m=141597517132682): everything gets stuck.
>>
>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> Reported-and-Tested-by: Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
>> CC: konrad.wilk@oracle.com
>> ---
>>
>> Konrad, this fixes an actual bug, at least on OMAP5. It should have no
>> bad side effects on any other platforms as far as I can tell. It should
>> go in 4.5.
>
> From Andrii's mail, there is a bad side effect. We can receive spurious
> interrupt.
>
> On V1, you said that you tried this patch on midway. I would prefer if
> you give a try on platform that would really be used (such as xgene or
> seattle). As we know Midway won't be used in prod.
And maybe give a try to gicv3 too as it's common code.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-11-20 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 10:53 [PATCH v2 for-4.5] xen/arm: clear UIE on hypervisor entry Stefano Stabellini
2014-11-20 11:02 ` Julien Grall
2014-11-20 11:06 ` Julien Grall [this message]
2014-11-20 15:54 ` Stefano Stabellini
2014-11-20 16:46 ` Julien Grall
2014-11-21 14:13 ` Julien Grall
2014-11-20 11:08 ` Stefano Stabellini
2014-11-20 16:47 ` Ian Campbell
2014-11-20 20:17 ` Konrad Rzeszutek Wilk
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=546DCB30.6040400@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=andrii.tseglytskyi@globallogic.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.