From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: James Harper <james.harper@bendigoit.com.au>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.2.2 / fixed vanilla kernel 3.7.10 / GPLPV r956 passes my torture test
Date: Mon, 10 Jun 2013 12:44:30 +0200 [thread overview]
Message-ID: <51B5AE0E.9050301@hfp.de> (raw)
In-Reply-To: <6035A0D088A63A46850C3988ED045A4B5C206CA4@BITCOM1.int.sbss.com.au>
Hello James,
> Thanks for the feedback. If you feel like doing some more testing, the latest
> commit includes a very experimental tmem driver that does write-through caching
> on the pagefile.
Sorry, I don't have time to test/validate experimental features. I think
it would be great if you could introduce some "stable release concept"
in GPLPV. I think most users (including me) will find it difficult to
identify the latest stable release of GPLPV.
My tests always try to validate (as far as this is possible at all) a
stable Xen setup.
Regards Andreas
next prev parent reply other threads:[~2013-06-10 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 18:29 Xen 4.2.2 / fixed vanilla kernel 3.7.10 / GPLPV r956 passes my torture test Andreas Kinzler
2013-06-08 0:45 ` James Harper
2013-06-10 10:44 ` Andreas Kinzler [this message]
2013-06-08 11:18 ` Wei Liu
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=51B5AE0E.9050301@hfp.de \
--to=ml-xen-devel@hfp.de \
--cc=james.harper@bendigoit.com.au \
--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.