On Sat, Jun 6, 2015 at 2:50 AM, Jeffrey Hugo wrote:
> If you still wish to scope out a capability based alternative, would you
> please provide some details about how you envision it working? An example
> of the API, how it would be used, future usecases that might be covered by
> it, etc. That
On 6/4/2015 7:09 PM, Ohad Ben-Cohen wrote:
On Tue, May 26, 2015 at 11:36 PM, Lina Iyer wrote:
Just to make sure I understand, is this how your scenario is solved?
- c1 goes down
- c0 goes down, carries information about shared resources
- c1 takes HWLOCK and calls into SCM, stuck handling FIQs
On Tue, May 26, 2015 at 11:36 PM, Lina Iyer wrote:
>> Just to make sure I understand, is this how your scenario is solved?
>>
>> - c1 goes down
>> - c0 goes down, carries information about shared resources
>> - c1 takes HWLOCK and calls into SCM, stuck handling FIQs
>> - c0 wants to call into SCM
On Sat, May 23 2015 at 01:36 -0600, Ohad Ben-Cohen wrote:
Hi Lina,
On Mon, May 18, 2015 at 6:03 PM, Lina Iyer wrote:
The lock in question is used differently than traditional locks across
processors. This lock helps synchronizes context transition from
non-secure to secure on the same processo
Hi Lina,
On Mon, May 18, 2015 at 6:03 PM, Lina Iyer wrote:
> The lock in question is used differently than traditional locks across
> processors. This lock helps synchronizes context transition from
> non-secure to secure on the same processor.
>
> The usecase, goes like this. In cpuidle, any cor
On Tue, May 19 2015 at 14:13 -0600, Andy Gross wrote:
On Mon, May 18, 2015 at 09:03:02AM -0600, Lina Iyer wrote:
On Sat, May 16 2015 at 03:03 -0600, Ohad Ben-Cohen wrote:
>On Mon, May 11, 2015 at 5:46 PM, Lina Iyer wrote:
>>On Sat, May 09 2015 at 03:25 -0600, Ohad Ben-Cohen wrote:
>>>On Fri, Ma
On Mon, May 18, 2015 at 09:03:02AM -0600, Lina Iyer wrote:
> On Sat, May 16 2015 at 03:03 -0600, Ohad Ben-Cohen wrote:
> >On Mon, May 11, 2015 at 5:46 PM, Lina Iyer wrote:
> >>On Sat, May 09 2015 at 03:25 -0600, Ohad Ben-Cohen wrote:
> >>>On Fri, May 1, 2015 at 8:07 PM, Lina Iyer wrote:
> >>>Let'
On Sat, May 16 2015 at 03:03 -0600, Ohad Ben-Cohen wrote:
On Mon, May 11, 2015 at 5:46 PM, Lina Iyer wrote:
On Sat, May 09 2015 at 03:25 -0600, Ohad Ben-Cohen wrote:
On Fri, May 1, 2015 at 8:07 PM, Lina Iyer wrote:
Let's discuss whether we really want to expose this functionality
under the sa
On Mon, May 11, 2015 at 5:46 PM, Lina Iyer wrote:
> On Sat, May 09 2015 at 03:25 -0600, Ohad Ben-Cohen wrote:
>> On Fri, May 1, 2015 at 8:07 PM, Lina Iyer wrote:
>> Let's discuss whether we really want to expose this functionality
>> under the same hwspinlock API or not.
>>
>> In this new mode, u
On Sat, May 09 2015 at 03:25 -0600, Ohad Ben-Cohen wrote:
Hi Lina,
On Fri, May 1, 2015 at 8:07 PM, Lina Iyer wrote:
Some uses of the hwspinlock could be that one entity acquires the lock
and the other entity releases the lock. This allows for a serialized
traversal path from the locking entity
Hi Lina,
On Fri, May 1, 2015 at 8:07 PM, Lina Iyer wrote:
> Some uses of the hwspinlock could be that one entity acquires the lock
> and the other entity releases the lock. This allows for a serialized
> traversal path from the locking entity to the other.
>
> For example, the cpuidle entry from
Some uses of the hwspinlock could be that one entity acquires the lock
and the other entity releases the lock. This allows for a serialized
traversal path from the locking entity to the other.
For example, the cpuidle entry from Linux to the firmware to power down
the core, can be serialized acros
12 matches
Mail list logo
