linux-kernel - Re: [PATCH V5 5/7] irqchip, gicv3, its: Probe ITS in the ACPI way.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5756F143.9050801@semihalf.com>
Date:	Tue, 7 Jun 2016 18:07:31 +0200
From:	Tomasz Nowicki <tn@...ihalf.com>
To:	Marc Zyngier <marc.zyngier@....com>
Cc:	tglx@...utronix.de, jason@...edaemon.net, rjw@...ysocki.net,
	lorenzo.pieralisi@....com, robert.richter@...iumnetworks.com,
	shijie.huang@....com, Suravee.Suthikulpanit@....com,
	hanjun.guo@...aro.org, al.stone@...aro.org, mw@...ihalf.com,
	graeme.gregory@...aro.org, Catalin.Marinas@....com,
	will.deacon@....com, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	ddaney.cavm@...il.com, okaya@...eaurora.org,
	andrea.gallo@...aro.org
Subject: Re: [PATCH V5 5/7] irqchip, gicv3, its: Probe ITS in the ACPI way.

On 04.06.2016 13:55, Marc Zyngier wrote:
> On Tue, 31 May 2016 13:19:42 +0200
> Tomasz Nowicki <tn@...ihalf.com> wrote:
>
>> ITS is prepared for being initialized different than DT,
>> therefore we can initialize it in ACPI way. We collect register base
>> address from MADT table and pass mandatory info to firmware-agnostic
>> ITS init call.
>>
>> Note that we are using here IORT lib to register ITS domain which
>> then can be found and used on to build another PCI MSI domain
>> in hierarchical stack domain.
>>
>> Signed-off-by: Tomasz Nowicki <tn@...ihalf.com>

[...]

>>   }
>>
>> +#ifdef CONFIG_ACPI
>> +
>> +#define ACPI_GICV3_ITS_MEM_SIZE (2 * SZ_64K)
>
> SZ_128k?
>
>> +
>> +static int __init gic_acpi_parse_madt_its(struct acpi_subtable_header *header,
>> +					  const unsigned long end)
>> +{
>> +	struct acpi_madt_generic_translator *its_entry;
>> +	struct fwnode_handle *dom_handle;
>> +	struct resource res;
>> +	int err;
>> +
>> +	its_entry = (struct acpi_madt_generic_translator *)header;
>> +	res.start = its_entry->base_address;
>> +	res.end = its_entry->base_address + ACPI_GICV3_ITS_MEM_SIZE - 1;
>> +
>> +	dom_handle = irq_domain_alloc_fwnode((void *)its_entry->base_address);
>> +	if (!dom_handle) {
>> +		pr_err("ITS@%pa: Unable to allocate GICv3 ITS domain token\n",
>> +		       &res.start);
>> +		return -ENOMEM;
>> +	}
>> +
>> +	err = iort_register_domain_token(its_entry->translation_id, dom_handle);
>> +	if (err) {
>> +		pr_err("ITS@%pa: Unable to register GICv3 ITS domain token (ITS ID %d) to IORT\n",
>> +		       &res.start, its_entry->translation_id);
>> +		goto dom_err;
>> +	}
>> +
>> +	err = its_probe_one(&res, dom_handle);
>> +	if (!err)
>> +		return 0;
>> +
>> +	iort_deregister_domain_token(its_entry->translation_id);
>> +dom_err:
>> +	irq_domain_free_fwnode(dom_handle);
>> +	return err;
>> +}
>> +
>> +void __init its_acpi_probe(void)
>
> Should be static.
>
>> +{
>> +	if (acpi_table_parse_madt(ACPI_MADT_TYPE_GENERIC_TRANSLATOR,
>> +				  gic_acpi_parse_madt_its, 0) <= 0)
>> +		pr_info("No valid GIC ITS entries exist\n");
>
> We already have a message further down, no need to shout twice.
>
>> +}
>> +#else
>> +static inline void __init its_acpi_probe(struct irq_domain *parent_domain) { }
>
> Drop the inline, the compiler can figure out that by itself.
>

I will address all above comments in next series.

Tomasz