From: Marc Zyngier <marc.zyngier@arm.com>
To: Majun <majun258@huawei.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
robert.moore@intel.com, lenb@kernel.org, lv.zheng@intel.com,
rafael.j.wysocki@intel.com, devel@acpica.org,
mark.rutland@arm.com, robh+dt@kernel.org, jason@lakedaemon.net
Cc: dingtianhong@huawei.com, guohanjun@huawei.com
Subject: Re: [RFC PATCH 0/3] Add a new flag for ITS device to control indirect route
Date: Thu, 1 Dec 2016 09:07:14 +0000 [thread overview]
Message-ID: <3ce161a7-ee63-a018-4a75-9e7520143d97@arm.com> (raw)
In-Reply-To: <1480578360-9268-1-git-send-email-majun258@huawei.com>
On 01/12/16 07:45, Majun wrote:
> From: MaJun <majun258@huawei.com>
>
> For current ITS driver, two level table (indirect route) is enabled when the memory used
> for LPI route table over the limit(64KB * 2) size. But this function impact the
> performance of LPI interrupt actually because need more time to look up the table.
Are you implying that your ITS doesn't have a cache to lookup the most
active devices, hence performing a full lookup on each interrupt?
Anyway, doing this as a DT quirk doesn't feel right. Please use the ITS
quirk infrastructure.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-12-01 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 7:45 [RFC PATCH 0/3] Add a new flag for ITS device to control indirect route Majun
2016-12-01 7:45 ` [RFC PATCH 1/3]Binding: Add a new property string in ITS node to control the two-level route function Majun
2016-12-01 7:45 ` [RFC PATCH 2/3] irqchip/gicv3-its: add a new flag to control indirect route in DT mode Majun
2016-12-01 7:46 ` [RFC PATCH 3/3]irqchip/gicv3-its: Add a new flag to control indirect route in ACPI mode Majun
2016-12-01 9:07 ` Marc Zyngier [this message]
2016-12-02 9:29 ` [RFC PATCH 0/3] Add a new flag for ITS device to control indirect route majun (Euler7)
2016-12-02 9:35 ` Marc Zyngier
2016-12-05 3:11 ` majun (Euler7)
2016-12-05 9:00 ` Marc Zyngier
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=3ce161a7-ee63-a018-4a75-9e7520143d97@arm.com \
--to=marc.zyngier@arm.com \
--cc=devel@acpica.org \
--cc=dingtianhong@huawei.com \
--cc=guohanjun@huawei.com \
--cc=jason@lakedaemon.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=majun258@huawei.com \
--cc=mark.rutland@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=robh+dt@kernel.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