search for: x86_featur

...Brian, The Atom1-buildbot buildslave has been failing for a few days but I don't think the problem lies in the LLVM/Clang source. From the logs at http://lab.llvm.org:8011/builders/clang-atom-d2700-ubuntu-rel/builds/13632 (and newer builds): ******************** TEST 'Clang :: Driver/x86_features.s' FAILED ******************** Test has no run line! ******************** I don't see this file in the repository. Could you (or one of your colleagues) take a look? Thanks Daniel Sanders Leading Software Design Engineer, MIPS Processor IP Imagination Technologies Limited ww...

...by doing paravirt switching at > runtime. You're not addressing the problem. Your fixing the symptom, which is wrong to begin with. > The alternative use-case is a runtime version of apply_alternatives() > (not posted with this patch-set) that can be used for some safe subset > of X86_FEATUREs. This could be useful in conjunction with the ongoing > late microcode loading work that Mihai Carabas and others have been > working on. This has been discussed to death before and there is no safe subset as long as this hasn't been resolved: https://lore.kernel.org/lkml/alpine.DEB...

Attempting to boot xVM dom0 for the first time on a Toshiba Tecra M2 running 75a. Getting a panic immediately after selecting xVM from the grub menu: panic[cpu0]/thread=f502c020: Processor does not support PAE This is a 2000 MHz Pentium-M, which I thought was PAE-capable.

...s a test-and-set spinlock, where unlocked means 'val == 0'. That just happens to not be the case now, but it was for a fair while. > The alternative use-case is a runtime version of apply_alternatives() > (not posted with this patch-set) that can be used for some safe subset > of X86_FEATUREs. This could be useful in conjunction with the ongoing > late microcode loading work that Mihai Carabas and others have been > working on. The whole late-microcode loading stuff is crazy already; you're making it take double bonghits. > Also, there are points of similarity with the...

...s a test-and-set spinlock, where unlocked means 'val == 0'. That just happens to not be the case now, but it was for a fair while. > The alternative use-case is a runtime version of apply_alternatives() > (not posted with this patch-set) that can be used for some safe subset > of X86_FEATUREs. This could be useful in conjunction with the ongoing > late microcode loading work that Mihai Carabas and others have been > working on. The whole late-microcode loading stuff is crazy already; you're making it take double bonghits. > Also, there are points of similarity with the...

...in ~60 seconds) = 62,901,545 > > # toggle native spinlocks > [ 1656.117175] Writes: Total: 1113888840 Max/Min: 0/0 Fail: 0 > # native spinlocks (in ~60 seconds) = 2,228,295 > > The alternatives testing is more limited with it being used to rewrite > mostly harmless X86_FEATUREs with load in the background. > > Patches also at: > > ssh://git at github.com/terminus/linux.git alternatives-rfc-upstream-v1 > > Please review. > > Thanks > Ankur > > [1] The precise change in memory footprint depends on config options > but the following...