All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Requirements for retpoline in Linux 4.15 (was: Re: Linux 4.15)
Date: Mon, 29 Jan 2018 12:19:44 +0100	[thread overview]
Message-ID: <5520835.tArHHOCcxE@merkaba> (raw)
In-Reply-To: <5326624.8I3Ve3uUFt@merkaba>

Martin Steigerwald - 29.01.18, 11:42:
> > Try removing .cache.mk which has 'remembered' that your GCC doesn't
> > support retpoline.
> 
> I bet there have been "*.cache.mk" files around from previous pre gcc-7.3
> compiles.
> 
> Trying again after
> 
> % find -name ".cache.mk" -delete
> 
> on kernel source tree.
> 
> Will report back.

The whole thing works:

% grep . /sys/devices/system/cpu/vulnerabilities/*                                                       
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic 
retpoline

I bet the virtualbox modules compiled by virtualbox-dkms will taint the 
support, but I bet sooner or later they will support retpoline as well. 
(Another reason to switch to KVM one day.)

Thank you.
-- 
Martin

  reply	other threads:[~2018-01-29 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-28 21:52 Linux 4.15 Linus Torvalds
2018-01-29  9:41 ` Requirements for retpoline in Linux 4.15 (was: Re: Linux 4.15) Martin Steigerwald
2018-01-29  9:53   ` David Woodhouse
2018-01-29 10:42     ` Martin Steigerwald
2018-01-29 11:19       ` Martin Steigerwald [this message]
2018-01-29 11:35         ` David Woodhouse
2018-01-30  3:43           ` Josh Poimboeuf

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=5520835.tArHHOCcxE@merkaba \
    --to=martin@lichtvoll.de \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.