From: Jan Kiszka <jan.kiszka@siemens.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] kvm-kmod-2.6.31.5
Date: Wed, 28 Oct 2009 13:51:35 +0100 [thread overview]
Message-ID: <4AE83E57.9060409@siemens.com> (raw)
In-Reply-To: <90D306BE6EBC8D428A824FBBA7A3113D012F07D55B@ronja.maurer-it.com>
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
next prev parent reply other threads:[~2009-10-28 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 17:26 [ANNOUNCE] kvm-kmod-2.6.31.5 Jan Kiszka
2009-10-26 21:25 ` Alexander Graf
2009-10-27 8:25 ` Jan Kiszka
2009-10-27 10:39 ` Avi Kivity
2009-10-27 11:16 ` Jan Kiszka
2009-10-28 11:19 ` Dietmar Maurer
2009-10-28 11:55 ` Jan Kiszka
2009-10-28 12:15 ` Dietmar Maurer
2009-10-28 12:51 ` Jan Kiszka [this message]
2009-10-28 12:56 ` Dietmar Maurer
2009-10-28 17:24 ` Jan Kiszka
2009-10-29 8:11 ` Dietmar Maurer
2009-10-29 8:32 ` Jan Kiszka
[not found] ` <90D306BE6EBC8D428A824FBBA7A3113D012F07D55C@ronja.maurer-it.com>
2009-10-28 12:41 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE83E57.9060409@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=dietmar@proxmox.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.