From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] xenomai patch
Date: Sat, 19 Jun 2010 12:35:05 -0400 [thread overview]
Message-ID: <20100619163505.GA27220@Krystal> (raw)
In-Reply-To: <2e75fbaa06b4a3fbc88260d305d50455@datapatterns.co.in>
* thirumalai.p (thirumalai.p at datapatterns.co.in) wrote:
> Hi,
> I am using Linux-2.6.19 kernel patched with xenomai-2.3. I just want to
> apply LTTng patch on this kernel and try find some randomly occuring
> problem in my system. First tell us is this correct way to go? Like you
> have provided some seperate patch set for xenomai in my earlier
> communication. If so is there any one generating LTTng patch set for
> xenomai tree seperately?
Sorry, I don't provide support for Xenomai specifically. I try to keep
up with Linux mainline ;)
>
> One more thing. Earlier we tried for x86 arch[xenomai is not patched] it
> worked fine for me. I try to apply patch for my kernel[xenomai patched]
> with LTTng patch and try to compile for powerpc and it is generating some
> warnings and errors at the end of compilation.
>
> The output as follows
> .
> .
> .....
> CC arch/ppc/mm/tlb.o
> In file included from arch/ppc/include/asm/atomic.h:455,
> from arch/ppc/include/asm/bitops.h:42,
> from include/linux/bitops.h:9,
> from include/linux/kernel.h:15,
> from arch/ppc/mm/tlb.c:26:
> include/asm-generic/atomic.h: In function 'atomic_long_cmpxchg':
> include/asm-generic/atomic.h:275: warning: implicit declaration of function
> 'cmpxchg'
> include/asm-generic/atomic.h: In function 'atomic_long_xchg':
> include/asm-generic/atomic.h:282: warning: implicit declaration of function
> 'xchg'
Make sure #include <asm/system.h> is present in your
arch/ppc/include/asm/atomic.h file.
Mathieu
> .............
> ............
> ..............
>
> Thank you
> Thirumalai
>
>
>
>
> **************** CAUTION - Disclaimer *****************This email may contain confidential and privileged material for the
> sole use of the intended recipient(s). Any review, use, retention, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Also, email is susceptible to data corruption, interception, tampering, unauthorized amendment and viruses. We only send and receive emails on the basis that we are not liable for any such corruption, interception, tampering, amendment or viruses or any consequence thereof.
> *********** End of Disclaimer ***********DataPatterns ITS Group**********
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
parent reply other threads:[~2010-06-19 16:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2e75fbaa06b4a3fbc88260d305d50455@datapatterns.co.in>]
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=20100619163505.GA27220@Krystal \
--to=compudj@krystal.dyndns.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