Dietmar Maurer wrote: > Well, we use the ubuntu tree: > > http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=summary > > They have a few more patches applied: > > http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=history;f=include/asm-x86/msr.h;h=cfe169475b5b50a448326ef3c34f50100ac83faf;hb=HEAD > > Seems the last two patches cause the problem. > > I just wonder if we need those bariers or not? > > http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=198b348d96c9769153e72ca2461f8d841ddff1cc The barrier is not our problem regarding the kvm-kmod build, it's the addition of native_read_tsc (http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=d10247b31c2be39ab3109015bc99bbd2ba6554d4). Do you know if there is anything to tell this ubuntu-patched kernel apart from a vanilla version? If so, we could adjust the check in x86/external-module-compat.h to avoid this breakage. Locally, you could simply comment out the double definition for now. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
