From: "Christopher Friesen" <cfriesen@nortel.com>
To: jerome lacoste <jerome.lacoste@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] make it easy to test new kernels
Date: Wed, 25 Jan 2006 16:50:52 -0600 [thread overview]
Message-ID: <43D800CC.4090901@nortel.com> (raw)
In-Reply-To: <5a2cf1f60601251430k5823e7dald12c9b5f8bc297be@mail.gmail.com>
jerome lacoste wrote:
> Now, will all these talks about virtualization, I wonder if it will be
> possible one day to just download a new virtualized test OS and test
> it without rebooting the main one. I could always allocate 10 G to a
> test system on my disk. As long as I don't have to reboot.
A large portion of kernel issues are found in the hardware support,
which is difficult to test in a virtualized environment.
However, something like this could ensure that the APIs handle random
garbage, that POSIX works properly, etc...
Chris
next prev parent reply other threads:[~2006-01-25 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 22:30 [RFC] make it easy to test new kernels jerome lacoste
2006-01-25 22:50 ` Christopher Friesen [this message]
2006-01-25 23:02 ` Jesper Juhl
2006-01-30 14:52 ` Tejun
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=43D800CC.4090901@nortel.com \
--to=cfriesen@nortel.com \
--cc=jerome.lacoste@gmail.com \
--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 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.