From: Jan Kiszka <jan.kiszka@siemens.com>
To: Bernhard Kohl <bernhard.kohl@nsn.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: external module: support building against Windriver 2.0 (kernel 2.6.21)
Date: Thu, 12 Mar 2009 19:06:01 +0100 [thread overview]
Message-ID: <49B94F09.90302@siemens.com> (raw)
In-Reply-To: <loom.20090312T173612-632@post.gmane.org>
Bernhard Kohl wrote:
> This is needed to compile kvm in a Windriver 2.0 distribution
> (kernel 2.6.21). This kernel has an include file marker.h, but
> trace_mark is not defined there. So the compat code in
> kernel/include-compat/linux/marker.h is not included.
I bet this is because Wind River patched some variant of LTTng into
their kernel.
However, I'm unsure if supporting significantly modified distribution
kernels is in the scope of this compat layer. If it is ok for the
maintainers, you should try to make the test more Wind River specific
(did you check that there is no side-effect for normal <= 2.6.21
kernels?) and maybe add a comment.
Jan
>
> Signed-off-by: Bernhard Kohl <bernhard.kohl@nsn.com>
> ---
> kernel/external-module-compat-comm.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/external-module-compat-comm.h
> b/kernel/external-module-compat-comm.h
> index a14cea2..e40501e 100644
> --- a/kernel/external-module-compat-comm.h
> +++ b/kernel/external-module-compat-comm.h
> @@ -25,6 +25,10 @@
> # undef CONFIG_KVM_TRACE
> #endif
>
> +#if LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,21)
> +#define trace_mark(args...) ((void)0)
> +#endif
> +
> /*
> * 2.6.16 does not have GFP_NOWAIT
> */
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-03-12 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 17:37 [PATCH] kvm: external module: support building against Windriver 2.0 (kernel 2.6.21) Bernhard Kohl
2009-03-12 18:06 ` Jan Kiszka [this message]
2009-03-13 15:12 ` Bernhard Kohl
2009-03-15 10:24 ` Avi Kivity
2009-03-16 23:03 ` Bernhard Kohl
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=49B94F09.90302@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=bernhard.kohl@nsn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox