From: Paul Larson <plars@linuxtestproject.org>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Balloon driver tests
Date: Thu, 16 Jun 2005 16:22:43 -0500 [thread overview]
Message-ID: <42B1EDA3.6010804@linuxtestproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Here's a small set of tests I've written for the balloon driver. I'm
sure there's more that could be tested, but it's a start. Can/should
these go in the tests directory?
Here's a brief description of each and a tarball since it would be
cumbersome to send them all inline:
balloon01: Test read from /proc/xen/balloon
balloon02: Echo a number higher than current requested allocation to
/proc/xen/balloon, cat balloon and see that requested target changed.
balloon03: Echo a number lower than current requested allocation to
/proc/xen/balloon, cat balloon and see that requested target changed.
balloon04: Allocate some memory for the domain, then use
/proc/xen/balloon to reduce available memory to less than what is allocated
balloon05: Try to give /proc/xen/balloon a value larger than the
available RAM in the system.
balloon06: Try to give /proc/xen/balloon a value way too low, such as 4k
balloon07: Open /proc/xen/balloon as non-root user, expect -EACCES
balloon08: Write 1 byte to /proc/xen/balloon, expect -EBADMSG
balloon09: Write >64 bytes to /proc/xen/balloon, expect -EFBIG
Thanks,
Paul Larson
[-- Attachment #2: balloon.tgz --]
[-- Type: application/x-compressed, Size: 3271 bytes --]
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2005-06-16 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 21:22 Paul Larson [this message]
2005-06-16 22:34 ` Balloon driver tests Kip Macy
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=42B1EDA3.6010804@linuxtestproject.org \
--to=plars@linuxtestproject.org \
--cc=xen-devel@lists.xensource.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.