From: Julien Grall <julien@xen.org>
To: Stefano Stabellini <stefano.stabellini@xilinx.com>
Cc: Peng Fan <peng.fan@nxp.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"maz@kernel.org" <maz@kernel.org>,
George Dunlap <George.Dunlap@citrix.com>,
Wei Xu <xuwei5@hisilicon.com>,
Bertrand Marquis <Bertrand.Marquis@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>, nd <nd@arm.com>,
Julien Grall <julien.grall.oss@gmail.com>
Subject: Re: [PATCH v2] xen/arm: implement GICD_I[S/C]ACTIVER reads
Date: Fri, 17 Apr 2020 17:47:52 +0100 [thread overview]
Message-ID: <651d7cd7-6a42-8898-72db-263bf6f7ea98@xen.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2004170930420.13631@sstabellini-ThinkPad-T480s>
On 17/04/2020 17:31, Stefano Stabellini wrote:
> On Fri, 17 Apr 2020, Julien Grall wrote:
>> Hi Bertrand,
>>
>> On 17/04/2020 16:16, Bertrand Marquis wrote:
>>> It seems that the problem is a bit bigger then expected and will need more
>>> discussion and thinking.
>>> I did some research on my side and there are several design possible
>>> depending on what should be the goal performance or real-time behaviour
>>> (going from just give the status we have to fire a service interrupts when
>>> any interrupts is acked by a guest to refresh our internal status).
>>>
>>> In the short term, could we not agree to fix the typo by returning always 0
>>> and start a discussion on the vgic implementation ?
>>
>> I have already pointed out multiple time now ([1], [2]) that I would not
>> oppose the temporary solution. I think this is a matter of someone (Stefano?)
>> to submit it :).
>>
>> Cheers,
>>
>> [1] https://lists.xenproject.org/archives/html/xen-devel/2019-11/msg01642.html
>> [2] https://lists.xenproject.org/archives/html/xen-devel/2020-04/msg00459.html
>
> I can submit it. Julien, would you prefer the plain always return 0
> patch, or would you prefer if I tried to get the latest ISACTIVER
> information (like this patch does) but only for the local processor?
Always returning 0.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2020-04-17 16:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 2:34 [Xen-devel] [PATCH v2] xen/arm: implement GICD_I[S/C]ACTIVER reads Stefano Stabellini
2020-03-28 11:52 ` Julien Grall
2020-03-30 16:35 ` Stefano Stabellini
2020-03-30 21:19 ` Julien Grall
2020-04-01 0:57 ` Stefano Stabellini
2020-04-01 8:30 ` Julien Grall
2020-04-01 9:54 ` Bertrand Marquis
2020-04-01 17:02 ` George Dunlap
2020-04-01 17:56 ` Julien Grall
2020-04-01 17:23 ` Julien Grall
2020-04-02 8:17 ` Bertrand Marquis
2020-04-02 17:19 ` Stefano Stabellini
2020-04-02 18:52 ` Julien Grall
2020-04-03 8:47 ` Marc Zyngier
2020-04-03 10:43 ` George Dunlap
2020-04-03 10:59 ` Marc Zyngier
2020-04-03 11:15 ` George Dunlap
2020-04-03 11:16 ` Julien Grall
2020-04-03 16:18 ` Stefano Stabellini
2020-04-03 16:23 ` Julien Grall
2020-04-03 17:46 ` Julien Grall
2020-04-03 19:41 ` Stefano Stabellini
2020-04-03 20:27 ` Julien Grall
2020-04-06 17:58 ` George Dunlap
2020-04-06 18:47 ` Julien Grall
2020-04-07 16:16 ` George Dunlap
2020-04-07 16:25 ` Bertrand Marquis
2020-04-07 16:52 ` Julien Grall
2020-04-07 16:50 ` Julien Grall
2020-04-07 16:56 ` Julien Grall
2020-04-07 18:16 ` George Dunlap
2020-04-07 19:58 ` Julien Grall
2020-04-09 1:26 ` Stefano Stabellini
2020-04-09 12:56 ` Julien Grall
2020-04-09 13:00 ` Julien Grall
2020-04-17 15:16 ` Bertrand Marquis
2020-04-17 16:07 ` Julien Grall
2020-04-17 16:31 ` Stefano Stabellini
2020-04-17 16:47 ` Julien Grall [this message]
2020-04-08 15:54 ` Julien Grall
2020-03-31 0:05 ` [Xen-devel] " Julien Grall
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=651d7cd7-6a42-8898-72db-263bf6f7ea98@xen.org \
--to=julien@xen.org \
--cc=Bertrand.Marquis@arm.com \
--cc=George.Dunlap@citrix.com \
--cc=julien.grall.oss@gmail.com \
--cc=maz@kernel.org \
--cc=nd@arm.com \
--cc=peng.fan@nxp.com \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@xilinx.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xuwei5@hisilicon.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).