[LITMUS^RT] RFC: record interrupt interference with Feather-Trace

[Christopher Kenna]

I don't see anything about using raw and non-raw get CPU variables in
the linked LWN article. It doesn't look like either version of the
get_cpu_var is disabling preemptions or migrations.

On Mon, Jan 30, 2012 at 1:59 PM, Glenn Elliott <gelliott at cs.unc.edu> wrote:
>
>> The first is the use of the __raw_get_cpu_var function versus the
>> __get_cpu_var function. I was wondering in what situation to use one
>> versus the other? It looks like (from what I could make out in the
>> code) that the two functions differ only when CONFIG_DEBUG_PREEMPT is
>> enabled (the kernel configuration help says something about printing
>> warnings if kernel code uses it in a preemption-unsafe way).
>
> This is new to PREEMPT_RT.  See the Per-CPU section here: http://lwn.net/Articles/464180/
>
>
>>
>>
>> 2012/1/27 Björn Brandenburg <bbb at mpi-sws.org>:
>>>
>>> On Jan 26, 2012, at 6:27 PM, Christopher Kenna wrote:
>>>> The public repository <http://www.litmus-rt.org/src/litmus-rt.git>
>>>> currently has a master and staging branch. I assume that development
>>>> stuff like this would go elsewhere.
>>>> If you need to reply to me
>>>> directly (off of the list) to talk about where to go to find them
>>>> and/or get a public key from me, that is okay. Alternatively, if you
>>>> still have your UNC account, you could push it to the CVS/git machine
>>>> here.
>>>
>>> I already did that when I first posted the patches. It should be in the branch wip-ft-irq-flag on the UNC servers (both cvs.cs... and  jupiter-cs.cs...).
>>>
>>> It may make sense to have public development branches at some point (bitbucket.org? github.org?), but for now I think it's easier for me to just push it to the UNC systems.
>>>
>>> - Björn
>>>
>>>
>>> _______________________________________________
>>> litmus-dev mailing list
>>> litmus-dev at lists.litmus-rt.org
>>> https://lists.litmus-rt.org/listinfo/litmus-dev
>>
>> _______________________________________________
>> litmus-dev mailing list
>> litmus-dev at lists.litmus-rt.org
>> https://lists.litmus-rt.org/listinfo/litmus-dev
>
>
> _______________________________________________
> litmus-dev mailing list
> litmus-dev at lists.litmus-rt.org
> https://lists.litmus-rt.org/listinfo/litmus-dev