From: Bian Naimeng <biannm@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH]Fix building error.
Date: Thu, 23 Dec 2010 14:45:40 +0800 [thread overview]
Message-ID: <4D12F014.4010600@cn.fujitsu.com> (raw)
In-Reply-To: <ABE3F4B7-6A3A-4339-999D-A3D41CC63147@gmail.com>
Garrett Cooper wrote:
> On Dec 20, 2010, at 11:31 PM, Bian Naimeng wrote:
>
>> CAI Qian wrote:
>>>> Could you tell me which kernels are this test fit to?
>>> It is hard to tell. The old kernel might decide to back-port this feature.
>> I see.
>>
>> Would you like tell me what's the test required?
>>
>> If the test is good, i think it should pass on old kernel which had back-port
>> this feature, otherwise the back-port procedure is incorrect.
>
> Yes, assuming features are tied to specific versions is a bad idea; a lot of code in LTP does this in an effort to be correct as to when it was first implemented, but it's wrong because there are various groups who may have backported support for distro or product specific reasons :)...
>
>>>> If there is old KSM interface, and this test can not work correctly on
>>>> it, i think we should fix the test, it should not do anything but reports
>>>> "This test is unsupported!"
>>> Anyway, it would be more code to test here and there rather than kernel version. Isn't LTP's guideline to only support the latest and greatest kernels?
>
> I wish. It would make life a lot easier, but that isn't the way that things are today (esp the folks on here that are running ancient versions of Redhat... *cough*)... and given that trying to track Linux changes is like trying to forecast the weather, stuff is always changing -- for better or for worse -- which makes it a pain for everyone else sitting out on the sidelines, like LTP, because Linux kernel devs don't actively engage test projects.
> There isn't really a line drawn in the sand as far as what is and isn't supported by LTP, except between 2.4 and 2.6 kernels, and even that is murky in spots.
Yes.
However, many people use the LTP to test their own linux system, if those kernel
is not support KSM, at least we should make sure they can build successfully.
Regards
Bian
> Thanks,
> -Garrett
>
--
Regards
Bian Naimeng
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-12-23 6:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 6:15 [LTP] [PATCH]Fix building error Bian Naimeng
2010-12-21 6:20 ` Bian Naimeng
2010-12-21 6:39 ` CAI Qian
2010-12-21 7:02 ` Bian Naimeng
2010-12-21 7:11 ` CAI Qian
2010-12-21 7:31 ` Bian Naimeng
2010-12-21 8:05 ` Garrett Cooper
2010-12-23 6:45 ` Bian Naimeng [this message]
2010-12-23 7:02 ` CAI Qian
2010-12-23 7:13 ` Bian Naimeng
2010-12-23 19:25 ` Garrett Cooper
2010-12-27 5:27 ` CAI Qian
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=4D12F014.4010600@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.com \
/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