From: Petr Tesarik <ptesarik@suse.cz>
To: James Dolan <jamesdolan@clear.net.nz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel testing in a VM good idea?
Date: Mon, 29 Jun 2009 17:25:04 +0200 [thread overview]
Message-ID: <1246289104.7698.15.camel@nathan.suse.cz> (raw)
In-Reply-To: <20090627185749.065bcab4@linux-uvcl.site>
James Dolan píše v So 27. 06. 2009 v 18:57 -0400:
> Are there any disadvantages to testing/developing a kernel in a VM ? (i
> luck the availability of hardware)
AFAICS the only unsurmountable problems you might encounter is timing
and performance. You can't predict how real hardware will work when it
comes to CPU and memory caches, system buses, hardware interrupts, large
CPU counts, NUMA factors, etc. But if any of those were of any concern
to you, you wouldn't have asked, I guess. ;-)
So, no, I don't think there are any important disadvantages when using
virtualized environment.
Petr Tesarik
SUSE Linux
prev parent reply other threads:[~2009-06-29 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 22:57 Kernel testing in a VM good idea? James Dolan
2009-06-27 7:15 ` Aioanei Rares
2009-06-27 9:07 ` Maciej Rutecki
2009-06-29 8:32 ` Duane Griffin
2009-06-29 15:25 ` Petr Tesarik [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=1246289104.7698.15.camel@nathan.suse.cz \
--to=ptesarik@suse.cz \
--cc=jamesdolan@clear.net.nz \
--cc=linux-kernel@vger.kernel.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