From: "Jan Beulich" <JBeulich@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Igor Druzhinin <igor.druzhinin@citrix.com>,
osstest-admin@xenproject.org,
xen-devel <xen-devel@lists.xenproject.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [xen-unstable test] 112855: regressions - trouble: blocked/broken/fail/pass
Date: Tue, 29 Aug 2017 07:12:32 -0600 [thread overview]
Message-ID: <59A584600200007800175030@prv-mh.provo.novell.com> (raw)
In-Reply-To: <07d3bd14-4b6b-ff84-e711-11a9fdf4406e@oracle.com>
>>> On 29.08.17 at 14:45, <boris.ostrovsky@oracle.com> wrote:
> I am somewhat puzzled though by the fact that I haven't seen this in my
> testing --- I was creating/destroying very large guests (> 1TB) in
> parallel so there must have been loops over high orders and I never had
> a watchdog go off. And my dom0s were quite large too while the one in
> this flight is only 512M.
I guess much depends on memory access latencies on the particular
systems.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-08-29 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 3:15 [xen-unstable test] 112855: regressions - trouble: blocked/broken/fail/pass osstest service owner
2017-08-25 13:40 ` Jan Beulich
2017-08-25 17:14 ` Boris Ostrovsky
2017-08-28 7:25 ` Jan Beulich
2017-08-28 13:57 ` Boris Ostrovsky
2017-08-28 14:02 ` Jan Beulich
2017-08-28 14:24 ` Boris Ostrovsky
2017-08-28 14:52 ` Jan Beulich
2017-08-28 15:36 ` Boris Ostrovsky
2017-08-29 8:07 ` Jan Beulich
2017-08-29 12:45 ` Boris Ostrovsky
2017-08-29 13:12 ` Jan Beulich [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=59A584600200007800175030@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=igor.druzhinin@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=roger.pau@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 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.