xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Wei Liu <wei.liu2@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: [OSSTEST PATCH] mg-repro-setup: --autoalloc-nofree option
Date: Thu, 19 Oct 2017 11:15:57 +0100	[thread overview]
Message-ID: <1508408157-14909-1-git-send-email-ian.jackson@eu.citrix.com> (raw)

This lets you run the automatic allocator within your own task, so you
get to keep whatever it found.

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
CC: Wei Liu <wei.liu2@citrix.com>
---
 mg-repro-setup | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/mg-repro-setup b/mg-repro-setup
index 25cbc78..0bafb53 100755
--- a/mg-repro-setup
+++ b/mg-repro-setup
@@ -58,6 +58,7 @@ logfile=tmp/mg-repro-setup.log
 duration=28d
 blessing=play
 skipcapture=true
+autoalloc=false
 
 while true; do
 	case "$1" in
@@ -72,6 +73,7 @@ while true; do
 	-t?*)		duration=${arg#-t}		;;
 	--rogue)	duration=''			;;
 	--capture)	skipcapture=false		;;
+	--autoalloc-nofree) autoalloc=true		;;
 	-l*)		logfile=${arg#-l}		;;
 	-r!*)		adjustsets+=("${arg#-r}")	;;
 	-r*=*)		adjustsets+=("${arg#-r}")	;;
@@ -204,7 +206,10 @@ if $skipcapture; then adjrunvar skip_testids "capture-logs*"; fi
 
 progress "executing ..."
 
-OSSTEST_NOALLOCATE=1 \
+if ! $autoalloc; then
+	export OSSTEST_NOALLOCATE=1
+fi
+
 ./mg-execute-flight -B$blessing -f$refflight --progress-fd=2 \
 	"${mgexecflags[@]}" $flight
 
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2017-10-19 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 10:15 Ian Jackson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-19 10:23 [OSSTEST PATCH] mg-repro-setup: --autoalloc-nofree option Ian Jackson

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=1508408157-14909-1-git-send-email-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).