From: Matthew Wilcox <willy@infradead.org>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [shmem] a067b3644b: vm-scalability.throughput -73.2% regression
Date: Sun, 08 Jul 2018 18:10:26 -0700 [thread overview]
Message-ID: <20180709011026.GA11700@bombadil.infradead.org> (raw)
In-Reply-To: <20180704062532.GC10005@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Wed, Jul 04, 2018 at 02:25:32PM +0800, Ye Xiaolong wrote:
> Hi, Matthew
>
> The issue should be fixed now, could you have a try?
I could really use some help diagnosing this. Is there a way to ssh
into the lkp virtual machine while it's running, or boot it to a command
prompt, or something else I can use to (eg) run strace?
When I boot the same kernel with the ktest system (which I do know how to
ssh into), running usemem with the same parameters successfully forks four
tasks. So I'm a little stuck.
next prev parent reply other threads:[~2018-07-09 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 7:34 [lkp-robot] [shmem] a067b3644b: vm-scalability.throughput -73.2% regression kernel test robot
2018-06-20 20:27 ` Matthew Wilcox
2018-06-22 7:35 ` Ye Xiaolong
2018-07-04 6:25 ` Ye Xiaolong
2018-07-06 2:59 ` Matthew Wilcox
2018-07-09 1:10 ` Matthew Wilcox [this message]
2018-07-09 2:47 ` Ye Xiaolong
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=20180709011026.GA11700@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=lkp@lists.01.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.