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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fd064e0c-d828-6555-7bf5-768fc2c1b142@arm.com>
Date:   Fri, 26 Jan 2018 11:39:22 +0000
From:   Sudeep Holla <sudeep.holla@....com>
To:     Lina Iyer <ilina@...eaurora.org>
Cc:     Sudeep Holla <sudeep.holla@....com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Jason Cooper <jason@...edaemon.net>,
        Marc Zyngier <marc.zyngier@....com>,
        open list <linux-kernel@...r.kernel.org>,
        linux-arm-msm@...r.kernel.org, Stephen Boyd <sboyd@...eaurora.org>,
        "Nayak, Rajendra" <rnayak@...eaurora.org>, asathyak@...eaurora.org
Subject: Re: [PATCH RFC 0/4] irqchip: qcom: add support for PDC interrupt
 controller



On 25/01/18 20:05, Lina Iyer wrote:
> On Thu, Jan 25 2018 at 18:43 +0000, Sudeep Holla wrote:
>>

[...]

>> It may have some advantages to decentralize but will that not cause
>> issues in complex systems ? I assume even modem and other processors can
>> access and configure these wakeup interrupts. What happens if 2 such
>> processors try to access it at the same time ?
>>
> Every processor in the SoC has its own PDC and does exactly the same
> thing in SW. The hardware blocks are replicated for each of the
> 'subsystem' and they behave similarly.
> 

Ah that explains a lot.

-- 
Regards,
Sudeep

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ