Displaying 10 results from an estimated 10 matches for "sibyt".
Did you mean:
sibyte
2011 Jan 17
8
[PATCH] sched: provide scheduler_ipi() callback in response to smp_send_reschedule()
...| 1 +
arch/blackfin/mach-common/smp.c | 3 ++-
arch/cris/arch-v32/kernel/smp.c | 13 ++++++++-----
arch/ia64/kernel/irq_ia64.c | 2 ++
arch/ia64/xen/irq_xen.c | 10 +++++++++-
arch/m32r/kernel/smp.c | 2 +-
arch/mips/kernel/smtc.c | 1 +
arch/mips/sibyte/bcm1480/smp.c | 7 +++----
arch/mips/sibyte/sb1250/smp.c | 7 +++----
arch/mn10300/kernel/smp.c | 2 +-
arch/parisc/kernel/smp.c | 1 +
arch/powerpc/kernel/smp.c | 1 +
arch/s390/kernel/smp.c | 6 +++---
arch/sh/kernel/smp.c | 2 ++
ar...
2011 Jan 17
8
[PATCH] sched: provide scheduler_ipi() callback in response to smp_send_reschedule()
...| 1 +
arch/blackfin/mach-common/smp.c | 3 ++-
arch/cris/arch-v32/kernel/smp.c | 13 ++++++++-----
arch/ia64/kernel/irq_ia64.c | 2 ++
arch/ia64/xen/irq_xen.c | 10 +++++++++-
arch/m32r/kernel/smp.c | 2 +-
arch/mips/kernel/smtc.c | 1 +
arch/mips/sibyte/bcm1480/smp.c | 7 +++----
arch/mips/sibyte/sb1250/smp.c | 7 +++----
arch/mn10300/kernel/smp.c | 2 +-
arch/parisc/kernel/smp.c | 1 +
arch/powerpc/kernel/smp.c | 1 +
arch/s390/kernel/smp.c | 6 +++---
arch/sh/kernel/smp.c | 2 ++
ar...
2011 Jan 17
8
[PATCH] sched: provide scheduler_ipi() callback in response to smp_send_reschedule()
...| 1 +
arch/blackfin/mach-common/smp.c | 3 ++-
arch/cris/arch-v32/kernel/smp.c | 13 ++++++++-----
arch/ia64/kernel/irq_ia64.c | 2 ++
arch/ia64/xen/irq_xen.c | 10 +++++++++-
arch/m32r/kernel/smp.c | 2 +-
arch/mips/kernel/smtc.c | 1 +
arch/mips/sibyte/bcm1480/smp.c | 7 +++----
arch/mips/sibyte/sb1250/smp.c | 7 +++----
arch/mn10300/kernel/smp.c | 2 +-
arch/parisc/kernel/smp.c | 1 +
arch/powerpc/kernel/smp.c | 1 +
arch/s390/kernel/smp.c | 6 +++---
arch/sh/kernel/smp.c | 2 ++
ar...
2016 Jan 15
3
[v3,11/41] mips: reuse asm-generic/barrier.h
On 01/14/2016 04:47 PM, Paul E. McKenney wrote:
> On Thu, Jan 14, 2016 at 03:33:40PM -0800, Leonid Yegoshin wrote:
>> Don't be fooled here by words "ordered" and "completed" - it is HW
>> design items and actually written poorly.
>> Just assume that SYNC_MB is absolutely the same as SYNC for any CPU
>> and coherent device (besides performance).
2016 Jan 15
3
[v3,11/41] mips: reuse asm-generic/barrier.h
On 01/14/2016 04:47 PM, Paul E. McKenney wrote:
> On Thu, Jan 14, 2016 at 03:33:40PM -0800, Leonid Yegoshin wrote:
>> Don't be fooled here by words "ordered" and "completed" - it is HW
>> design items and actually written poorly.
>> Just assume that SYNC_MB is absolutely the same as SYNC for any CPU
>> and coherent device (besides performance).
2005 Apr 04
0
problem about initramfs
dear friend.
i have mips board with BCM sibyte 1125CPU(use board sibyte 1250 swarm.)
i use linux-kernel 2.6.12-rc1 download from linux-mips.com
i use kernel 2.4.26 before this time, it's work ok at 2.4.26 with
Ramdisk-busybox
when i try to use ramdisk in 2.6.1x version, i found that ramdisk i not
exist,
i don't known how to use it...
2016 Jan 28
0
[v3,11/41] mips: reuse asm-generic/barrier.h
...t all - yes, it is still possible that SYNC on
>> some systems can be too heavy or even harmful, nobody tested that.
> I don't recall being asked;
In http://patchwork.linux-mips.org/patch/10505/ the very last mesg
exchange is:
Maciej,
do you have an R4000 / R4600 / R5000 / R7000 / SiByte system at hand to
test this?
...
Ralf
Maciej W. Rozycki
<http://patchwork.linux-mips.org/project/linux-mips/list/?submitter=79>
- June 5, 2015, 9:18 p.m.
On Fri, 5 Jun 2015, Ralf Baechle wrote:
> do you have an R4000 / R4600 / R5000 / R7000 / SiByte system at hand to
> test thi...
2016 Jan 28
0
[v3,11/41] mips: reuse asm-generic/barrier.h
...ux/kernel/1601.3/03080.html>.
> There's a reference to an older message of mine there too. I hope this
> answers your questions.
>
> Maciej
In http://patchwork.linux-mips.org/patch/10505/the very last mesg
exchange is:
Maciej,
do you have an R4000 / R4600 / R5000 / R7000 / SiByte system at hand to
test this?
...
Ralf
Maciej W. Rozycki- June 5, 2015, 9:18 p.m.
On Fri, 5 Jun 2015, Ralf Baechle wrote:
> do you have an R4000 / R4600 / R5000 / R7000 / SiByte system at hand to
> test this?
I should be able to check R4400 (that is virtually the same as R4000)
next...
2016 Jan 27
1
[v3,11/41] mips: reuse asm-generic/barrier.h
On Thu, Jan 14, 2016 at 04:47:53PM -0800, Paul E. McKenney wrote:
> So you need to build a different kernel for some types of MIPS systems?
Yes. We can't really do without. Classic MIPS code is not relocatable
without the complexity of PIC code as used by ELF DSOs - and their
performanc penalty. Plus we have a number of architecture revisions
ovr the decades, big and little endian, 32
2016 Jan 27
1
[v3,11/41] mips: reuse asm-generic/barrier.h
On Thu, Jan 14, 2016 at 04:47:53PM -0800, Paul E. McKenney wrote:
> So you need to build a different kernel for some types of MIPS systems?
Yes. We can't really do without. Classic MIPS code is not relocatable
without the complexity of PIC code as used by ELF DSOs - and their
performanc penalty. Plus we have a number of architecture revisions
ovr the decades, big and little endian, 32