<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - non-portable x86/x86_64 inline assembly" href="https://bugs.freedesktop.org/show_bug.cgi?id=86997#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - non-portable x86/x86_64 inline assembly" href="https://bugs.freedesktop.org/show_bug.cgi?id=86997">bug 86997</a> from <a class="email" href="mailto:marcandre.lureau@gmail.com" title="Marc-Andre Lureau <marcandre.lureau@gmail.com>"> Marc-Andre Lureau</a> <pre>(In reply to Christophe Fergeau from <a href="show_bug.cgi?id=86997#c2">comment #2</a>) > Created <a href="attachment.cgi?id=110448" name="attach_110448" title="Use gcc builtin rather than asm for memory barriers">attachment 110448</a> <a href="attachment.cgi?id=110448&action=edit" title="Use gcc builtin rather than asm for memory barriers">[details]</a> <a href='page.cgi?id=splinter.html&bug=86997&attachment=110448'>[review]</a> [review] > Use gcc builtin rather than asm for memory barriers > > I actually have that patch in my local spice-protocol copy which I never > really tested... my understanding is that this is correct, I think we should try that in the coming upstream release. (if not there are a lot of mb defines in kernel arch/*/include/asm/barrier.h) (there are possibly better version of the ring, apparently adapted from Tim Deegan and Andrew Warfield)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>