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] [day] [month] [year] [list]
Date:	Mon, 24 Sep 2012 09:35:30 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Chanho Min <chanho0207@...il.com>
Cc:	Marc Zyngier <marc.zyngier@....com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Will Deacon <will.deacon@....com>,
	Rob Herring <rob.herring@...xeda.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: gic: fix irq affinity mismatch.

On Mon, Sep 24, 2012 at 12:06:19PM +0900, Chanho Min wrote:
> Even if we set affinity to multiple cpus via procfs, gic_set_affinity
> allows to set one target only. But, '/proc/irq/xxx/smp_affinity' shows
> as we are successful in the setting of multiple affinity. Thus irq_data->
> affinity mismatches with the GICD_ITARGETSRs.
> 
> fix it as bellows.
> - Set the default affinity to the boot cpu in gic_dist_init. thereafter,
> irq_data->affinity will be set to default 1-bit affinity.
> - Even if we write multiple bits to smp_affinity, both irq_data and gic
> register will be set one cpu. procfs will show 1 bit affinity as well.

This has come up before.  There is no requirement to make the affinity
mask reflect back to userspace what the hardware is doing.  So, NAK.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ