All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waiman Long <waiman.long@hpe.com>
To: kbuild test robot <lkp@intel.com>
Cc: <kbuild-all@01.org>, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
	Borislav Petkov <bp@suse.de>, Andy Lutomirski <luto@kernel.org>,
	Dave Hansen <dave.hansen@intel.com>,
	Prarit Bhargava <prarit@redhat.com>,
	Scott J Norton <scott.norton@hpe.com>,
	Douglas Hatch <doug.hatch@hpe.com>,
	Randy Wright <rwright@hpe.com>
Subject: Re: [PATCH v6] x86/hpet: Reduce HPET counter read contention
Date: Mon, 15 Aug 2016 21:52:52 -0400	[thread overview]
Message-ID: <57B271F4.1000204@hpe.com> (raw)
In-Reply-To: <201608131029.f01SIkCT%fengguang.wu@intel.com>

On 08/12/2016 10:30 PM, kbuild test robot wrote:
> Hi Waiman,
>
> [auto build test ERROR on tip/auto-latest]
> [also build test ERROR on v4.8-rc1 next-20160812]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url:    https://github.com/0day-ci/linux/commits/Waiman-Long/x86-hpet-Reduce-HPET-counter-read-contention/20160813-090247
> config: x86_64-randconfig-s0-08131002 (attached as .config)
> compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
> reproduce:
>          # save the attached .config to linux build tree
>          make ARCH=x86_64
>
> All error/warnings (new ones prefixed by>>):
>
>>> arch/x86/kernel/hpet.c:791: error: unknown field 'lock' specified in initializer
>>> arch/x86/kernel/hpet.c:791: warning: missing braces around initializer
>     arch/x86/kernel/hpet.c:791: warning: (near initialization for 'hpet.<anonymous>.lock.val')
>
> vim +/lock +791 arch/x86/kernel/hpet.c
>
>     785			u32 value;
>     786		};
>     787		u64 lockval;
>     788	};
>     789	
>     790	static union hpet_lock hpet __cacheline_aligned = {
>   >  791		.lock = __ARCH_SPIN_LOCK_UNLOCKED,
>     792	};
>     793	
>     794	static cycle_t read_hpet(struct clocksource *cs)
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

The following additional patch should fix the build error. The error 
wasn't produced when I did my test build with the gcc 4.8.5 compiler. 
That was why I missed it.

Cheers,
Longman

----------------------------------

diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index 71127fe..0822688 100644
--- a/arch/x86/kernel/hpet.c
+++ b/arch/x86/kernel/hpet.c
@@ -788,7 +788,7 @@ union hpet_lock {
  };

  static union hpet_lock hpet __cacheline_aligned = {
-       .lock = __ARCH_SPIN_LOCK_UNLOCKED,
+       { .lock = __ARCH_SPIN_LOCK_UNLOCKED, },
  };

  static cycle_t read_hpet(struct clocksource *cs)

  reply	other threads:[~2016-08-16  2:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-13  0:59 [PATCH v6] x86/hpet: Reduce HPET counter read contention Waiman Long
2016-08-13  2:30 ` kbuild test robot
2016-08-16  1:52   ` Waiman Long [this message]
2016-08-25 18:50 ` Dave Hansen
2016-08-25 20:07   ` Waiman Long

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=57B271F4.1000204@hpe.com \
    --to=waiman.long@hpe.com \
    --cc=bp@suse.de \
    --cc=dave.hansen@intel.com \
    --cc=doug.hatch@hpe.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=prarit@redhat.com \
    --cc=rwright@hpe.com \
    --cc=scott.norton@hpe.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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.