From: sudhir kumar <smalikphy@gmail.com>
To: Martin Bligh <mbligh@google.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
Autotest mailing list <autotest@test.kernel.org>,
Lucas Meneghel Rodrigues <mrodrigu@redhat.com>,
Uri Lublin <uril@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Autotest] [AUTOTEST] [PATCH 1/2] Add latest LTP test in autotest
Date: Mon, 13 Jul 2009 10:15:33 +0530 [thread overview]
Message-ID: <a50cf5ab0907122145v2b83fb5h20585b5062bdbe5d@mail.gmail.com> (raw)
In-Reply-To: <33307c790907061137h3da12536q47517b1662498793@mail.gmail.com>
On Tue, Jul 7, 2009 at 12:07 AM, Martin Bligh<mbligh@google.com> wrote:
>>> Issues: LTP has a history of some of the testcases getting broken.
>
> Right, that's always the concern with doing this.
>
>>> Anyways
>>> that has nothing to worry about with respect to autotest. One of the known issue
>>> is broken memory controller issue with latest kernels(cgroups and memory
>>> resource controller enabled kernels). The workaround for them I use is to
>>> disable or delete those tests from ltp source and tar it again with the same
>>> name. Though people might use different workarounds for it.
>
> OK, Can we encapsulate this into the wrapper though, rather than making
> people do it manually? in the existing ltp.patch or something?
>
I have rebased the patches and updated the existing ltp.patch. I will
be sending them soon.
Also for runningn ltp under kvm I have generated a patch kvm_ltp.patch
whose purpose is same as of ltp.patch but only for kvm guests. i will
be sending the results of execution on the guest as well as on bare
metal. Thanks everyone for your comments!!
--
Sudhir Kumar
prev parent reply other threads:[~2009-07-13 4:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 5:40 [AUTOTEST] [PATCH 1/2] Add latest LTP test in autotest sudhir kumar
2009-07-06 6:58 ` Lucas Meneghel Rodrigues
2009-07-06 18:37 ` [Autotest] " Martin Bligh
2009-07-07 7:24 ` sudhir kumar
2009-07-07 15:31 ` Lucas Meneghel Rodrigues
2009-07-08 4:22 ` sudhir kumar
2009-07-08 4:40 ` Martin Bligh
2009-07-08 9:25 ` Dor Laor
2009-07-08 9:30 ` sudhir kumar
2009-07-07 17:45 ` Martin Bligh
2009-07-08 4:17 ` sudhir kumar
2009-07-08 10:19 ` Subrata Modak
2009-07-08 10:19 ` [LTP] " Subrata Modak
2009-07-08 10:19 ` Subrata Modak
2009-07-08 15:05 ` [LTP] " Martin Bligh
2009-07-08 15:05 ` Martin Bligh
2009-07-08 23:05 ` [LTP] " Mike Frysinger
2009-07-08 23:05 ` Mike Frysinger
2009-07-13 4:45 ` sudhir kumar [this message]
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=a50cf5ab0907122145v2b83fb5h20585b5062bdbe5d@mail.gmail.com \
--to=smalikphy@gmail.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=mbligh@google.com \
--cc=mrodrigu@redhat.com \
--cc=uril@redhat.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 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.