From: Fengguang Wu <fengguang.wu@intel.com>
To: Steven Noonan <steven@uplinklabs.net>
Cc: Dave Hansen <dave.hansen@intel.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: [compiler/gcc4] a9f180345f5: -100.0% last_state.is_incomplete_run
Date: Tue, 30 Sep 2014 16:14:12 +0800 [thread overview]
Message-ID: <20140930081412.GF9561@wfg-t540p.sh.intel.com> (raw)
Hi Steven,
FYI, we noticed that your commit a9f180345f5378ac87d80ed0bea55ba421d83859
("compiler/gcc4: Make quirk for asm_volatile_goto() unconditional") fixed
a number of machine boot failures in our LKP test farm. This is really helpful!
Our gcc version is 4.9.1 (Debian 4.9.1-11).
569d6557ab957d6 a9f180345f5378ac87d80ed0b
--------------- -------------------------
%stddev %change %stddev
\ | /
1 ± 0% -100.0% 0 ± 0% lkp-st02/dd-write/5m-11HDD-RAID5-cfq-btrfs-100dd
1 ± 0% -100.0% 0 ± 0% TOTAL dmesg.kernel_BUG_at_fs/nfs/pagelist.c
569d6557ab957d6 a9f180345f5378ac87d80ed0b
--------------- -------------------------
1 ± 0% -100.0% 0 ± 0% lkp-st02/dd-write/5m-11HDD-RAID5-cfq-btrfs-100dd
1 ± 0% -100.0% 0 ± 0% TOTAL dmesg.Kernel_panic-not_syncing:Fatal_exception
569d6557ab957d6 a9f180345f5378ac87d80ed0b
--------------- -------------------------
1 ± 0% -100.0% 0 ± 0% lkp-st02/dd-write/5m-11HDD-RAID5-cfq-btrfs-100dd
1 ± 0% -100.0% 0 ± 0% TOTAL dmesg.invalid_opcode
569d6557ab957d6 a9f180345f5378ac87d80ed0b
--------------- -------------------------
1 ± 0% -100.0% 0 ± 0% ivb42/will-it-scale/futex4
1 ± 0% -100.0% 0 ± 0% ivb44/fsmark/1x-1t-1HDD-xfs-4M-60G-NoSync
1 ± 0% -100.0% 0 ± 0% ivb44/fsmark/1x-64t-1BRD_48G-btrfs-4M-40G-fsyncBeforeClose
1 ± 0% -100.0% 0 ± 0% lkp-bdw01/blogbench/1SSD-btrfs
1 ± 0% -100.0% 0 ± 0% lkp-hsw01/vm-scalability/300s-anon-rx-rand-mt
1 ± 0% -100.0% 0 ± 0% lkp-sbx04/will-it-scale/futex3
1 ± 0% -100.0% 0 ± 0% lkp-sbx04/will-it-scale/page_fault3
1 ± 0% -100.0% 0 ± 0% lkp-st02/dd-write/5m-11HDD-RAID5-cfq-btrfs-100dd
8 ± 0% -100.0% 0 ± 0% TOTAL last_state.is_incomplete_run
569d6557ab957d6 a9f180345f5378ac87d80ed0b
--------------- -------------------------
1 ± 0% -100.0% 0 ± 0% ivb42/will-it-scale/futex4
1 ± 0% -100.0% 0 ± 0% ivb44/fsmark/1x-1t-1HDD-xfs-4M-60G-NoSync
1 ± 0% -100.0% 0 ± 0% ivb44/fsmark/1x-64t-1BRD_48G-btrfs-4M-40G-fsyncBeforeClose
1 ± 0% -100.0% 0 ± 0% lkp-bdw01/blogbench/1SSD-btrfs
1 ± 0% -100.0% 0 ± 0% lkp-hsw01/vm-scalability/300s-anon-rx-rand-mt
1 ± 0% -100.0% 0 ± 0% lkp-sbx04/will-it-scale/futex3
1 ± 0% -100.0% 0 ± 0% lkp-sbx04/will-it-scale/page_fault3
1 ± 0% -100.0% 0 ± 0% lkp-st02/dd-write/5m-11HDD-RAID5-cfq-btrfs-100dd
8 ± 0% -100.0% 0 ± 0% TOTAL last_state.booting
Thanks,
Fengguang
next reply other threads:[~2014-09-30 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 8:14 Fengguang Wu [this message]
2014-10-03 0:46 ` Steven Noonan
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=20140930081412.GF9561@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=steven@uplinklabs.net \
/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
all inboxes | Powered by JetHome®