From: Ingo Molnar <mingo@kernel.org>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
luto@amacapital.net, bp@alien8.de, brgerst@gmail.com,
dvlasenk@redhat.com, hpa@zytor.com,
torvalds@linux-foundation.org, peterz@infradead.org,
tglx@linutronix.de
Subject: Re: [PATCH] [v3] x86/mm/mpx: Work around MPX erratum SKD046
Date: Thu, 12 May 2016 09:16:03 +0200 [thread overview]
Message-ID: <20160512071603.GA19835@gmail.com> (raw)
In-Reply-To: <20160512065040.GC30717@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
> > Changes from v1:
> > * Unconditionally enable workaround on all CPUs with MPX despite
> > whether we know it to be affected or not
> > * Add a pr_warn() when the workaround is active
> >
> > Changes from v2:
> > * fix build breakage from #ifdefs in bug.h
It now emits ugly warnings (x86-64 defconfig):
./arch/x86/include/asm/bugs.h:7:31: warning: ‘struct cpuinfo_x86’ declared inside parameter list
./arch/x86/include/asm/bugs.h:7:31: warning: its scope is only this definition or declaration, which is probably not what you want
Thanks,
Ingo
next prev parent reply other threads:[~2016-05-12 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 21:16 [PATCH] [v3] x86/mm/mpx: Work around MPX erratum SKD046 Dave Hansen
2016-05-12 6:50 ` Ingo Molnar
2016-05-12 7:16 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-04 20:53 [PATCH] [v2] x86, mpx: Workaround for MPX erratum Dave Hansen
2016-05-05 7:01 ` [PATCH v3] x86/mm/mpx: Work around MPX erratum SKD046 Ingo Molnar
2016-05-05 7:26 ` Ingo Molnar
2016-05-05 17:03 ` Dave Hansen
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=20160512071603.GA19835@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@sr71.net \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.