From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 1/5] irqchip/gicv3-its: Introduce two helper functions for accessing BASERn
Date: Mon, 6 Jun 2016 13:59:52 +0100 [thread overview]
Message-ID: <575573C8.6050409@arm.com> (raw)
In-Reply-To: <1465191636-6823-2-git-send-email-shankerd@codeaurora.org>
On 06/06/16 06:40, Shanker Donthineni wrote:
> This patch adds the two handy helper functions for reading and writing
> ITS BASERn register.
>
> Signed-off-by: Shanker Donthineni <shankerd@codeaurora.org>
> ---
> drivers/irqchip/irq-gic-v3-its.c | 32 +++++++++++++++++++++++++-------
> 1 file changed, 25 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
> index 5eb1f9e..6392c82 100644
> --- a/drivers/irqchip/irq-gic-v3-its.c
> +++ b/drivers/irqchip/irq-gic-v3-its.c
> @@ -56,13 +56,14 @@ struct its_collection {
> };
>
> /*
> - * The ITS_BASER structure - contains memory information and cached
> - * value of BASER register configuration.
> + * The ITS_BASER structure - contains memory information, cached value
> + * of BASER register configuration and register idx.
> */
> struct its_baser {
> void *base;
> u64 val;
> u32 order;
> + u32 idx;
> };
>
> /*
> @@ -824,6 +825,17 @@ static const char *its_base_type_string[] = {
> [GITS_BASER_TYPE_RESERVED7] = "Reserved (7)",
> };
>
> +static u64 its_read_baser(struct its_node *its, struct its_baser *baser)
> +{
> + return readq_relaxed(its->base + GITS_BASER + (baser->idx << 3));
> +}
> +
> +static void its_write_baser(struct its_node *its, struct its_baser *baser,
> + u64 val)
> +{
> + writeq_relaxed(val, its->base + GITS_BASER + (baser->idx << 3));
> +}
> +
> static void its_free_tables(struct its_node *its)
> {
> int i;
> @@ -863,14 +875,20 @@ static int its_alloc_tables(const char *node_name, struct its_node *its)
> its->device_ids = ids;
>
> for (i = 0; i < GITS_BASER_NR_REGS; i++) {
> - u64 val = readq_relaxed(its->base + GITS_BASER + i * 8);
> - u64 type = GITS_BASER_TYPE(val);
> - u64 entry_size = GITS_BASER_ENTRY_SIZE(val);
> + struct its_baser *baser = its->tables + i;
> int order = get_order(psz);
> + u64 val, type, entry_size;
> int alloc_pages;
> u64 tmp;
> void *base;
>
> + /* Record the register index */
> + baser->idx = i;
> +
> + val = its_read_baser(its, baser);
> + type = GITS_BASER_TYPE(val);
> + entry_size = GITS_BASER_ENTRY_SIZE(val);
> +
> if (type == GITS_BASER_TYPE_NONE)
> continue;
>
> @@ -939,8 +957,8 @@ retry_baser:
> val |= alloc_pages - 1;
> its->tables[i].val = val;
>
> - writeq_relaxed(val, its->base + GITS_BASER + i * 8);
> - tmp = readq_relaxed(its->base + GITS_BASER + i * 8);
> + its_write_baser(its, baser, val);
> + tmp = its_read_baser(its, baser);
>
> if ((val ^ tmp) & GITS_BASER_SHAREABILITY_MASK) {
> /*
>
Thanks to this abstraction, I now realize what I really hate about this
idea of caching stuff in the its_baser structure: you end up with
inconsistent data:
- You store something in baser->val
- You write something else using its_write_baser
- You read something else using its_read_baser
We have 3 sets of inconsistent data, and what they mean depends on
the context.
What I'm proposing is that its_write_baser always performs a read back,
and stores that read in baser->val. This gives us a more consistent
view of what's going on (the value we wanted, and what the HW is
actually capable of).
How about something like this, on top of my previous suggestion:
diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index 520d171..5591441 100644
--- a/drivers/irqchip/irq-gic-v3-its.c
+++ b/drivers/irqchip/irq-gic-v3-its.c
@@ -836,6 +836,7 @@ static void its_write_baser(struct its_node *its, struct its_baser *baser,
{
int idx = baser - its->tables;
writeq_relaxed(val, its->base + GITS_BASER + (idx << 3));
+ baser->val = its_read_baser(its, baser);
}
static int its_setup_baser(struct its_node *its, struct its_baser *baser,
@@ -891,7 +892,7 @@ retry_baser:
}
its_write_baser(its, baser, val);
- tmp = its_read_baser(its, baser);
+ tmp = baser->val;
if ((val ^ tmp) & GITS_BASER_SHAREABILITY_MASK) {
/*
@@ -939,7 +940,6 @@ retry_baser:
baser->order = order;
baser->base = base;
baser->psz = psz;
- baser->val = val;
tmp = indirect ? GITS_LVL1_ENTRY_SIZE : esz;
pr_info("ITS@%pa: allocated %d %s @%lx (%s, esz %d, psz %dK, shr %d)\n",
@@ -968,7 +968,7 @@ static bool its_parse_baser_device(struct its_node *its, struct its_baser *baser
* table by reading bit at offset '62' after writing '1' to it.
*/
its_write_baser(its, baser, val | GITS_BASER_INDIRECT);
- val = its_read_baser(its, baser);
+ val = baser->val;
indirect = !!(val & GITS_BASER_INDIRECT);
if (indirect) {
Thanks,
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Shanker Donthineni <shankerd@codeaurora.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Vikram Sethi <vikrams@codeaurora.org>,
Philip Elcan <pelcan@codeaurora.org>
Subject: Re: [PATCH V4 1/5] irqchip/gicv3-its: Introduce two helper functions for accessing BASERn
Date: Mon, 6 Jun 2016 13:59:52 +0100 [thread overview]
Message-ID: <575573C8.6050409@arm.com> (raw)
In-Reply-To: <1465191636-6823-2-git-send-email-shankerd@codeaurora.org>
On 06/06/16 06:40, Shanker Donthineni wrote:
> This patch adds the two handy helper functions for reading and writing
> ITS BASERn register.
>
> Signed-off-by: Shanker Donthineni <shankerd@codeaurora.org>
> ---
> drivers/irqchip/irq-gic-v3-its.c | 32 +++++++++++++++++++++++++-------
> 1 file changed, 25 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
> index 5eb1f9e..6392c82 100644
> --- a/drivers/irqchip/irq-gic-v3-its.c
> +++ b/drivers/irqchip/irq-gic-v3-its.c
> @@ -56,13 +56,14 @@ struct its_collection {
> };
>
> /*
> - * The ITS_BASER structure - contains memory information and cached
> - * value of BASER register configuration.
> + * The ITS_BASER structure - contains memory information, cached value
> + * of BASER register configuration and register idx.
> */
> struct its_baser {
> void *base;
> u64 val;
> u32 order;
> + u32 idx;
> };
>
> /*
> @@ -824,6 +825,17 @@ static const char *its_base_type_string[] = {
> [GITS_BASER_TYPE_RESERVED7] = "Reserved (7)",
> };
>
> +static u64 its_read_baser(struct its_node *its, struct its_baser *baser)
> +{
> + return readq_relaxed(its->base + GITS_BASER + (baser->idx << 3));
> +}
> +
> +static void its_write_baser(struct its_node *its, struct its_baser *baser,
> + u64 val)
> +{
> + writeq_relaxed(val, its->base + GITS_BASER + (baser->idx << 3));
> +}
> +
> static void its_free_tables(struct its_node *its)
> {
> int i;
> @@ -863,14 +875,20 @@ static int its_alloc_tables(const char *node_name, struct its_node *its)
> its->device_ids = ids;
>
> for (i = 0; i < GITS_BASER_NR_REGS; i++) {
> - u64 val = readq_relaxed(its->base + GITS_BASER + i * 8);
> - u64 type = GITS_BASER_TYPE(val);
> - u64 entry_size = GITS_BASER_ENTRY_SIZE(val);
> + struct its_baser *baser = its->tables + i;
> int order = get_order(psz);
> + u64 val, type, entry_size;
> int alloc_pages;
> u64 tmp;
> void *base;
>
> + /* Record the register index */
> + baser->idx = i;
> +
> + val = its_read_baser(its, baser);
> + type = GITS_BASER_TYPE(val);
> + entry_size = GITS_BASER_ENTRY_SIZE(val);
> +
> if (type == GITS_BASER_TYPE_NONE)
> continue;
>
> @@ -939,8 +957,8 @@ retry_baser:
> val |= alloc_pages - 1;
> its->tables[i].val = val;
>
> - writeq_relaxed(val, its->base + GITS_BASER + i * 8);
> - tmp = readq_relaxed(its->base + GITS_BASER + i * 8);
> + its_write_baser(its, baser, val);
> + tmp = its_read_baser(its, baser);
>
> if ((val ^ tmp) & GITS_BASER_SHAREABILITY_MASK) {
> /*
>
Thanks to this abstraction, I now realize what I really hate about this
idea of caching stuff in the its_baser structure: you end up with
inconsistent data:
- You store something in baser->val
- You write something else using its_write_baser
- You read something else using its_read_baser
We have 3 sets of inconsistent data, and what they mean depends on
the context.
What I'm proposing is that its_write_baser always performs a read back,
and stores that read in baser->val. This gives us a more consistent
view of what's going on (the value we wanted, and what the HW is
actually capable of).
How about something like this, on top of my previous suggestion:
diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index 520d171..5591441 100644
--- a/drivers/irqchip/irq-gic-v3-its.c
+++ b/drivers/irqchip/irq-gic-v3-its.c
@@ -836,6 +836,7 @@ static void its_write_baser(struct its_node *its, struct its_baser *baser,
{
int idx = baser - its->tables;
writeq_relaxed(val, its->base + GITS_BASER + (idx << 3));
+ baser->val = its_read_baser(its, baser);
}
static int its_setup_baser(struct its_node *its, struct its_baser *baser,
@@ -891,7 +892,7 @@ retry_baser:
}
its_write_baser(its, baser, val);
- tmp = its_read_baser(its, baser);
+ tmp = baser->val;
if ((val ^ tmp) & GITS_BASER_SHAREABILITY_MASK) {
/*
@@ -939,7 +940,6 @@ retry_baser:
baser->order = order;
baser->base = base;
baser->psz = psz;
- baser->val = val;
tmp = indirect ? GITS_LVL1_ENTRY_SIZE : esz;
pr_info("ITS@%pa: allocated %d %s @%lx (%s, esz %d, psz %dK, shr %d)\n",
@@ -968,7 +968,7 @@ static bool its_parse_baser_device(struct its_node *its, struct its_baser *baser
* table by reading bit at offset '62' after writing '1' to it.
*/
its_write_baser(its, baser, val | GITS_BASER_INDIRECT);
- val = its_read_baser(its, baser);
+ val = baser->val;
indirect = !!(val & GITS_BASER_INDIRECT);
if (indirect) {
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-06-06 12:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 5:40 [PATCH V4 0/5] Add two-level support for ITS device table Shanker Donthineni
2016-06-06 5:40 ` Shanker Donthineni
2016-06-06 5:40 ` [PATCH V4 1/5] irqchip/gicv3-its: Introduce two helper functions for accessing BASERn Shanker Donthineni
2016-06-06 5:40 ` Shanker Donthineni
2016-06-06 8:37 ` Marc Zyngier
2016-06-06 8:37 ` Marc Zyngier
2016-06-06 12:59 ` Marc Zyngier [this message]
2016-06-06 12:59 ` Marc Zyngier
2016-06-06 5:40 ` [PATCH V4 2/5] irqchip/gicv3-its: Add a new function for parsing device table BASERn Shanker Donthineni
2016-06-06 5:40 ` Shanker Donthineni
2016-06-06 5:40 ` [PATCH V4 3/5] irqchip/gicv3-its: Split its_alloc_tables() into two functions Shanker Donthineni
2016-06-06 5:40 ` Shanker Donthineni
2016-06-06 5:40 ` [PATCH V4 4/5] irqchip/gicv3-its: Remove an unused argument 'node_name' Shanker Donthineni
2016-06-06 5:40 ` Shanker Donthineni
2016-06-06 5:40 ` [PATCH V4 5/5] irqchip/gicv3-its: Implement two-level(indirect) device table support Shanker Donthineni
2016-06-06 5:40 ` Shanker Donthineni
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=575573C8.6050409@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.