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: Mon, 28 Aug 2017 08:52:03 -0600 [thread overview]
Message-ID: <59A44A330200007800174983@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1f3830ec-ee60-162d-a5f1-8df2017cf875@oracle.com>
>>> On 28.08.17 at 16:24, <boris.ostrovsky@oracle.com> wrote:
>>> As for periodically testing process_pending_softirqs() we may still want
>>> to do this in alloc_heap_pages(), even without CONFIG_SCRUB_DEBUG.
>> For my taste, alloc_heap_pages() is the wrong place for such
>> calls.
>
> But the loop is in alloc_heap_pages() --- where else would you be testing?
It can only reasonably be the callers of alloc_heap_pages() imo.
A single call to it should never trigger the watchdog, only calls
themselves sitting in a loop should be potential candidates for
causing such.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-28 14:52 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 [this message]
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
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=59A44A330200007800174983@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.