[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- To: Leonid Yegoshin <Leonid.Yegoshin@xxxxxxxxxx>
- From: "Maciej W. Rozycki" <macro@xxxxxxxxxx>
- Date: Wed, 27 Jan 2016 11:26:20 +0000
- Cc: linux-mips@xxxxxxxxxxxxxx, linux-ia64@xxxxxxxxxxxxxxx, "Michael S. Tsirkin" <mst@xxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Will Deacon <will.deacon@xxxxxxx>, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, "H. Peter Anvin" <hpa@xxxxxxxxx>, sparclinux@xxxxxxxxxxxxxxx, Ingo Molnar <mingo@xxxxxxxxxx>, linux-arch@xxxxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx, Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>, user-mode-linux-devel@xxxxxxxxxxxxxxxxxxxxx, linux-sh@xxxxxxxxxxxxxxx, Michael Ellerman <mpe@xxxxxxxxxxxxxx>, x86@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, Ingo Molnar <mingo@xxxxxxx>, paulmck@xxxxxxxxxxxxxxxxxx, linux-xtensa@xxxxxxxxxxxxxxxx, james.hogan@xxxxxxxxxx, Arnd Bergmann <arnd@xxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, adi-buildroot-devel@xxxxxxxxxxxxxxxxxxxxx, ddaney.cavm@xxxxxxxxx, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, linux-metag@xxxxxxxxxxxxxxx, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Ralf Baechle <ralf@xxxxxxxxxxxxxx>, Joe Perches <joe@xxxxxxxxxxx>, linuxppc-dev@xxxxxxxxxxxxxxxx, David Miller <davem@xxxxxxxxxxxxx>
- Delivery-date: Wed, 27 Jan 2016 11:26:39 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On Fri, 15 Jan 2016, Leonid Yegoshin wrote:
> > So you need to build a different kernel for some types of MIPS systems?
> > Or do you do boot-time rewriting, like a number of other arches do?
>
> I don't know. I would like to have responses. Ralf asked Maciej about old
> systems and that came nowhere. Even rewrite - don't know what to do with that:
> no lightweight SYNC or no SYNC at 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; mind that I might not get to messages I have
not been cc-ed in a timely manner and I may miss some altogether. With
the amount of mailing list traffic that passes by me my scanner may fail
to trigger. Sorry if this causes anybody trouble, but such is life.
Coincidentally, I have just posted some notes on SYNC in a different
thread, see <http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03080.html>.
There's a reference to an older message of mine there too. I hope this
answers your questions.
Maciej
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
- References:
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
|