From: Julien Grall <julien.grall@linaro.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: julien.grall@citrix.com, xen-devel@lists.xensource.com,
Ian.Campbell@citrix.com
Subject: Re: [PATCH v3 5/6] xen/arm: Only enable physical IRQs when the guest asks
Date: Wed, 11 Dec 2013 13:34:26 +0000 [thread overview]
Message-ID: <52A869E2.8010608@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1312111249360.7093@kaball.uk.xensource.com>
On 12/11/2013 12:50 PM, Stefano Stabellini wrote:
> On Tue, 10 Dec 2013, Julien Grall wrote:
>> On 12/10/2013 06:50 PM, Stefano Stabellini wrote:
>>> From: Julien Grall <julien.grall@linaro.org>
>>>
>>> Set/Unset IRQ_DISABLED from gic_irq_enable and gic_irq_disable.
>>> Enable IRQs when the guest requests it, not unconditionally at boot time.
>>>
>>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>> Signed-off-by: Julien Grall <julien.grall@citrix.com>
>>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>>>
>>> Changes in v2:
>>> - protect startup and shutdown with gic and desc locks.
>>
>> I think this change can move in patch #4 where you have implemented
>> gic_irq_enable/gic_irq_disable.
>
> I could move the gic spin_lock there, but the desc spin_lock needs to
> stay in patch #5. Not sure it's worth it.
Oh right, I didn't notice that __setup_irq is called with all the locks
taken.
--
Julien Grall
next prev parent reply other threads:[~2013-12-11 13:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 18:49 [PATCH v3 0/6] interrupt handling fixes Stefano Stabellini
2013-12-10 18:50 ` [PATCH v3 1/6] xen/arm: Physical IRQ is not always equal to virtual IRQ Stefano Stabellini
2013-12-10 18:50 ` [PATCH v3 2/6] xen/arm: track the state of guest IRQs Stefano Stabellini
2013-12-11 14:38 ` Ian Campbell
2013-12-11 19:00 ` Stefano Stabellini
2013-12-12 11:55 ` Ian Campbell
2013-12-12 14:55 ` Stefano Stabellini
2013-12-10 18:50 ` [PATCH v3 3/6] xen/arm: do not add a second irq to the LRs if one is already present Stefano Stabellini
2013-12-10 22:06 ` Julien Grall
2013-12-10 18:50 ` [PATCH v3 4/6] xen/arm: implement gic_irq_enable and gic_irq_disable Stefano Stabellini
2013-12-10 21:30 ` Julien Grall
2013-12-10 18:50 ` [PATCH v3 5/6] xen/arm: Only enable physical IRQs when the guest asks Stefano Stabellini
2013-12-10 21:11 ` Julien Grall
2013-12-11 12:50 ` Stefano Stabellini
2013-12-11 13:34 ` Julien Grall [this message]
2013-12-11 13:38 ` Julien Grall
2013-12-11 17:25 ` Stefano Stabellini
2013-12-10 18:50 ` [PATCH v3 6/6] xen/arm: disable a physical IRQ when the guest disables the corresponding IRQ Stefano Stabellini
2013-12-10 22:05 ` Julien Grall
2013-12-10 22:09 ` [PATCH v3 0/6] interrupt handling fixes Julien Grall
2013-12-11 14:19 ` 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=52A869E2.8010608@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.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 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).