From: Majun <majun258@huawei.com>
To: linux-kernel@vger.kernel.org, marc.zyngier@arm.com,
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, majun258@huawei.com
Subject: [RFC PATCH 0/3] Add a new flag for ITS device to control indirect route
Date: Thu, 1 Dec 2016 15:45:57 +0800 [thread overview]
Message-ID: <1480578360-9268-1-git-send-email-majun258@huawei.com> (raw)
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.
Although this function can save the memory needed, we'd better let the user
to decide enable or disable this function.
MaJun (3):
Binding: Add a new property string in ITS node to control the two-level route function
irqchip/gicv3-its:irqchip/gicv3-its: add a new flag to control indirect route in DT mode
irqchip/gicv3-its:irqchip/gicv3-its: Add a new flag to control indirect route function in ACPI mode.
.../bindings/interrupt-controller/arm,gic-v3.txt | 3 +++
drivers/irqchip/irq-gic-v3-its.c | 19 ++++++++++++++-----
include/acpi/actbl1.h | 3 ++-
3 files changed, 19 insertions(+), 6 deletions(-)
--
1.7.12.4
next reply other threads:[~2016-12-01 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 7:45 Majun [this message]
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 ` [RFC PATCH 0/3] Add a new flag for ITS device to control indirect route Marc Zyngier
2016-12-02 9:29 ` 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=1480578360-9268-1-git-send-email-majun258@huawei.com \
--to=majun258@huawei.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=marc.zyngier@arm.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