From: Julien Grall <julien.grall@arm.com>
To: Artem Mygaiev <artem_mygaiev@epam.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] xen/arm: Remove unused tnode variables in DT IRQ map parsing
Date: Tue, 6 Dec 2016 14:37:45 +0000 [thread overview]
Message-ID: <4749b2c4-89fb-7fe9-8b17-d463c79cec97@arm.com> (raw)
In-Reply-To: <07660b18-9835-02e2-a5d6-e6fc706d40ce@epam.com>
On 06/12/16 14:33, Artem Mygaiev wrote:
> Hi Julien
>
>
> On 06.12.16 16:19, Julien Grall wrote:
>> Hi Artem,
>>
>> On 06/12/16 13:57, Artem Mygaiev wrote:
>>> Remove unused tnode variables in device tree IRQ map parsing
>>
>> This description is slightly wrong, the variable are used but not the value.
> True
>>
>>> Coverity-ID 1381866, 1381867
>>>
>>> Signed-off-by: Artem Mygaiev <artem_mygaiev@epam.com>
>>
>> This code is from Linux (see drivers/of/irq.c) and I would prefer to keep it very similar as long as it does not lead to a bug:
> I understand, but in the kernel code tnode is used to safely decrement kobj refcount (e.g. in 4.8.12):
>
> 144 tnode = of_get_parent(old);
> 145 of_node_put(old);
> 146 old = tnode;
>
> AFAIU in Xen refcounts are dropped, so probably tnode can be dropped as a part of the infrastructure... no?
I have an item in my todo list to re-sync the device-tree code with
Linux. So we have a proper copy rather than a modified one.
Meanwhile, I would strongly prefer to keep this code as close as
possible from Linux. This tnode variable is harmless, so I stand on what
I said.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-06 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 13:57 [PATCH] xen/arm: Remove unused tnode variables in DT IRQ map parsing Artem Mygaiev
2016-12-06 14:19 ` Julien Grall
2016-12-06 14:33 ` Artem Mygaiev
2016-12-06 14:37 ` Julien Grall [this message]
2016-12-06 14:41 ` Artem Mygaiev
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=4749b2c4-89fb-7fe9-8b17-d463c79cec97@arm.com \
--to=julien.grall@arm.com \
--cc=artem_mygaiev@epam.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).