From: David Huff <dhuff@redhat.com>
To: Uri Lublin <uril@redhat.com>
Cc: Mike Burns <mburns@redhat.com>, kvm@vger.kernel.org, ulublin@redhat.com
Subject: Re: [PATCH][KVM-AUTOTEST][REPOST] Add ability to install custom kernel modules
Date: Mon, 01 Jun 2009 15:00:16 -0400 [thread overview]
Message-ID: <4A242540.4040006@redhat.com> (raw)
In-Reply-To: <4A24191C.6080705@redhat.com>
Uri Lublin wrote:
> Hi Mike,
>
> Can you load those kernel modules before running kvm-autotest (something
> like a setup script) ? And clean up when the run completes (cleanup
> script) ?
This can problay be done with the pre_command and post_command
parameters that I added in my previous patch.
Come to think of it, the whole custom kvm_install method is just a large
pre_command. I even used alot of the same code mike used when adding
this functionality.
Does it make sense to treat the custom install of kvm as one large
pre_command?
-D
prev parent reply other threads:[~2009-06-01 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 0:29 [PATCH][KVM-AUTOTEST][REPOST] Add ability to install custom kernel modules Mike Burns
2009-06-01 18:08 ` Uri Lublin
2009-06-01 18:16 ` Mike Burns
2009-06-01 19:00 ` David Huff [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=4A242540.4040006@redhat.com \
--to=dhuff@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mburns@redhat.com \
--cc=ulublin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox