All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, apatel@apm.com, psawargaonkar@apm.com
Subject: Re: [PATCH] xen/arm: introduce platform_need_explicit_eoi
Date: Mon, 30 Jun 2014 11:01:59 +0100	[thread overview]
Message-ID: <53B13597.70401@linaro.org> (raw)
In-Reply-To: <1403884302.3169.85.camel@kazak.uk.xensource.com>

On 06/27/2014 04:51 PM, Ian Campbell wrote:
> On Mon, 2014-06-23 at 11:43 +0100, Stefano Stabellini wrote:
>> I thought about this concurrency problem and I think I managed to
>> solve it correctly. The solution I used was introducing a new flag
>> called "GIC_IRQ_GUEST_MIGRATING". See:
>>
>> 1402504032-13267-4-git-send-email-stefano.stabellini@eu.citrix.com
> 
> So, I'm not sure whether I should apply this patch now or wait for that
> series to go in first. What should I do?

IIRC, I've asked Stefano to rewrote a bit the following paragraph.

"
> No need to find the pcpu that needs to write to GICC_DIR, because after
> "physical irq follow virtual irq" we always inject the virtual irq on
> the vcpu that is running on the pcpu that received the interrupt.
"

The "physical irq follow virtual irq" is part of the migration series
but this is not the reason that make GICC_DIR working. This is GIC
specific (even though, I can't find a clearly define behavior in the
specification).

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-06-30 10:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 13:35 [PATCH] xen/arm: introduce platform_need_explicit_eoi Stefano Stabellini
2014-06-20 14:11 ` Julien Grall
2014-06-20 14:27   ` Stefano Stabellini
2014-06-20 14:47     ` Julien Grall
2014-06-20 16:48       ` Stefano Stabellini
2014-06-20 16:59         ` Julien Grall
2014-06-20 17:40           ` Stefano Stabellini
2014-06-20 18:33             ` Julien Grall
2014-06-21 14:43               ` Stefano Stabellini
2014-06-21 14:59                 ` Julien Grall
2014-06-21 15:26                   ` Stefano Stabellini
2014-06-21 15:59                     ` Julien Grall
2014-06-23 10:43                       ` Stefano Stabellini
2014-06-27 15:51                         ` Ian Campbell
2014-06-30 10:01                           ` Julien Grall [this message]
2014-07-02 15:31                             ` Stefano Stabellini
2014-07-02 15:34                           ` Stefano Stabellini
2014-07-02 14:49 ` Julien Grall
2014-07-02 15:31   ` Stefano Stabellini

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=53B13597.70401@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=apatel@apm.com \
    --cc=psawargaonkar@apm.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.