Avi Kivity redhat.com> writes:
>
> Best would be to check for a Wind River kernel as this is likely to
> break on mainline Linux.
>
OK, I see, that's more complicated. We are currently thinking about to upgrade
our systems to an up-to-date kernel version. Then this patch is no longer
required.
Jan Kiszka wrote:
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
Jan Kiszka siemens.com> writes:
>
> 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
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 pa
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.
Signed-off-by: Bernhard Kohl
---
kernel/external-module-compat
