All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linaro.org>
To: lkp@lists.01.org
Subject: Re: [x86/tlb] ff9b625d26: stderr.Run:"Process_Creation":Fork_failed_at_iteration in unixbench test
Date: Mon, 21 Mar 2016 14:27:22 +0800	[thread overview]
Message-ID: <56EF944A.3060305@linaro.org> (raw)
In-Reply-To: <20160321061524.GA32569@yexl-desktop>

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]



On 03/21/2016 02:15 PM, Ye Xiaolong wrote:
> On Mon, Mar 21, 2016 at 01:51:59PM +0800, Alex Shi wrote:
>> Hi Xiaolong,
>>
>> Thanks for the info. Do you have any other benchmark data for this branch?
> 
> Hi, Alex
> 
> 0day system should have launched several benchmarks for branch with your
> commit, which specific benchmark are you interested in? I can search it
> in the system.

That should be memory related, multi-thread map/unmap benchmarks. guess
maybe tlbflush/hackbench/netperf/oltp/fio etc.

> 
> Thanks,
> Xiaolong.
>>
>> Regards
>> Alex
>>
>> On 03/21/2016 12:43 PM, Ye Xiaolong wrote:
>>> The unixbench is launched on a native OS.
>>>>>
>>>>> Any other benchmark did you test on any other machine? If so, what's the
>>>>> result you get?
>>> So far, we have just found issues with unixbench on two Ivy Bridge
>>> machine.

  reply	other threads:[~2016-03-21  6:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17  6:00 [x86/tlb] ff9b625d26: stderr.Run:"Process_Creation":Fork_failed_at_iteration in unixbench test kernel test robot
2016-03-17  9:07 ` Alex Shi
2016-03-18 14:27 ` Alex Shi
2016-03-21  4:43   ` Ye Xiaolong
2016-03-21  5:51     ` Alex Shi
2016-03-21  6:15       ` Ye Xiaolong
2016-03-21  6:27         ` Alex Shi [this message]
2016-03-21  6:33       ` Huang, Ying
2016-03-21  6:39         ` Alex Shi
2016-03-21  6:59           ` Huang, Ying

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=56EF944A.3060305@linaro.org \
    --to=alex.shi@linaro.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.