On 07/13/2015 11:11 AM, Michael Ellerman wrote:
> On Mon, 2015-07-13 at 10:54 +0530, Anshuman Khandual wrote:
>> On 07/10/2015 12:40 PM, Michael Neuling wrote:
>>> What's the performance impact of this? If you run this test with --fp,
>>> --altivec or --vector what is the impact of adding this pat
On Mon, 2015-07-13 at 10:54 +0530, Anshuman Khandual wrote:
> On 07/10/2015 12:40 PM, Michael Neuling wrote:
> > What's the performance impact of this? If you run this test with --fp,
> > --altivec or --vector what is the impact of adding this patch?
> >
> > http://ozlabs.org/~anton/junkcode/cont
On 07/10/2015 12:40 PM, Michael Neuling wrote:
> What's the performance impact of this? If you run this test with --fp,
> --altivec or --vector what is the impact of adding this patch?
>
> http://ozlabs.org/~anton/junkcode/context_switch2.c
>
> eg
> ./context_switch2 --fp 0 0
Please find th
What's the performance impact of this? If you run this test with --fp,
--altivec or --vector what is the impact of adding this patch?
http://ozlabs.org/~anton/junkcode/context_switch2.c
eg
./context_switch2 --fp 0 0
Mikey
On Thu, 2015-07-09 at 15:16 +0530, Anshuman Khandual wrote:
> This p
This patch enables facility unavailable exceptions for generic facility,
FPU, ALTIVEC and VSX in /proc/interrupts listing by incrementing their
newly added IRQ statistical counters as and when these exceptions happen.
This also adds couple of helper functions which will be called from within
the in
