xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Tim Deegan <tim@xen.org>,
	George Dunlap <george.dunlap@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] xen: arm: increase priority of SGIs used as IPIs
Date: Mon, 17 Mar 2014 11:34:08 +0000	[thread overview]
Message-ID: <5326DDB0.3030706@linaro.org> (raw)
In-Reply-To: <1395055741.4122.73.camel@kazak.uk.xensource.com>

Hi Ian,

On 03/17/2014 11:29 AM, Ian Campbell wrote:
> On Mon, 2014-03-17 at 10:02 +0000, Ian Campbell wrote:
>> On Sun, 2014-03-16 at 16:38 +0000, Stefano Stabellini wrote:
>>> On Thu, 13 Mar 2014, Oleksandr Tyshchenko wrote:
>>>> Hello, all.
>>>>
>>>> I tested this patch (with debug patch) when I was looking for solution
>>>> to fix "simultaneous cross-interrupts" (see 1.1):
>>>> http://lists.xenproject.org/archives/html/xen-devel/2014-01/msg02685.html
>>>> This patch didn't fix my issue.
>>>> When the solution was founded I forgot about this patch)
>>>>
>>>> Now I am using next solution:
>>>> http://marc.info/?l=xen-devel&m=139153089412362&w=2
>>>
>>> Speaking of which, it should probably be applied to xen-unstable now
>>> that the gate is open?
>>
>> Julien acked it but had a couple of minor comments which I wanted to
>> address today. I hope to repost later on.
> 
> Oh you meant the route irqs to dom0 patch in the link not the one in
> this thread. I'll pick that one up today as well I hope.

With the IPI patch, I don't think we need the route irqs to CPU0 patch
(at least for Xen 4.5). It would be better to backport it for Xen 4.4.

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-03-17 11:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 16:51 [PATCH] xen: arm: increase priority of SGIs used as IPIs Ian Campbell
2014-01-28 16:51 ` Ian Campbell
2014-01-28 17:50 ` Stefano Stabellini
2014-01-28 18:20   ` Oleksandr Tyshchenko
2014-03-13 12:26 ` Ian Campbell
2014-03-13 12:33 ` Julien Grall
2014-03-13 12:45   ` Ian Campbell
2014-03-13 12:56     ` Julien Grall
2014-03-13 13:35       ` Oleksandr Tyshchenko
2014-03-16 16:38         ` Stefano Stabellini
2014-03-17 10:02           ` Ian Campbell
2014-03-17 11:29             ` Ian Campbell
2014-03-17 11:34               ` Julien Grall [this message]
2014-03-17 11:36                 ` Ian Campbell
2014-03-17 12:42                   ` Ian Campbell

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=5326DDB0.3030706@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=oleksandr.tyshchenko@globallogic.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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).