From: "Lukáš Doktor" <ldoktor@redhat.com>
To: sudhir kumar <smalikphy@gmail.com>
Cc: KVM list <kvm@vger.kernel.org>, Jason Wang <jasowang@redhat.com>
Subject: Re: [KVM_AUTOTEST] add kvm hugepage variant and test
Date: Fri, 10 Jul 2009 08:48:26 +0200 [thread overview]
Message-ID: <4A56E43A.5060609@redhat.com> (raw)
In-Reply-To: <a50cf5ab0907092138s4fafbcfep98a9fe874fdc952e@mail.gmail.com>
- kvm_hugepages variant enables us to test if (host) kvm use of
hugepages works
- libhugetlbfs test inside of guest prove, that (guest) system is able
to handle hugepages (independently of whether guest uses hugepages).
This function is necessarily eg. if you want to run Oracle server inside
the guest.
So basically this are 2 independent things, but somehow connected. If
you want I can split the patches.
Dne 10.7.2009 06:38, sudhir kumar napsal(a):
> Why do you want to use a control file and put the libhugetlbfs as a
> variant of autotest in kvm? Just keeping the kvm_hugepages variant
> will not serve the same purpose ? I have been using hugetlbfs variant
> for a long but yes without pre script(I have done that manually)? Am I
> missing something here?
> Rest all looks fine to me except you need somewhere s/enaugh/enough
>
> 2009/7/9 Lukáš Doktor<ldoktor@redhat.com>:
>> This patch adds kvm_hugepage variant. It prepares the host system and start
>> vm with -mem-path option. It does not clean after itself, because it's
>> impossible to unmount and free hugepages before all guests are destroyed.
>>
>> There is also added autotest.libhugetlbfs test.
>>
>> I need to ask you what to do with change of qemu parameter. Newest versions
>> are using -mempath insted of -mem-path. This is impossible to fix using
>> current config file. I can see 2 solutions:
>> 1) direct change in kvm_vm.py (parse output and try another param)
>> 2) detect qemu capabilities outside and create additional layer (better for
>> future occurrence)
>>
>> Tested by:ldoktor@redhat.com on RHEL5.4 with kvm-83-72.el5
>>
>
>
>
next prev parent reply other threads:[~2009-07-10 6:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 9:24 [KVM_AUTOTEST] add kvm hugepage variant and test Lukáš Doktor
2009-07-09 12:30 ` Michael Goldish
2009-07-09 12:55 ` Lukáš Doktor
2009-07-10 4:38 ` sudhir kumar
2009-07-10 6:48 ` Lukáš Doktor [this message]
2009-07-10 8:03 ` Lukáš Doktor
2009-07-10 10:01 ` [KVM_AUTOTEST] add kvm hugepage variant Lukáš Doktor
2009-07-20 12:58 ` Lucas Meneghel Rodrigues
2009-07-21 16:04 ` Lukáš Doktor
2009-07-22 5:57 ` [Autotest] " sudhir kumar
2009-07-27 21:05 ` Lucas Meneghel Rodrigues
2009-07-10 10:04 ` [KVM_AUTOTEST] add autotest.libhugetlbfs test Lukáš Doktor
2009-07-10 10:37 ` sudhir kumar
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=4A56E43A.5060609@redhat.com \
--to=ldoktor@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=smalikphy@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;
as well as URLs for NNTP newsgroup(s).