All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Ford <aford173@gmail.com>
To: arm-soc <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org
Subject: Spectre and Cortex-A8/A9
Date: Wed, 9 May 2018 13:21:19 -0500	[thread overview]
Message-ID: <CAHCN7x+ghEW__YwgbXYO4g9HNKkwkQtXiswL1jihj0wwfKuR4Q@mail.gmail.com> (raw)

There is a lot of information pushed around the web about the Spectre
bug.  I went to ARM's support site and there are some patches
available from February that haven't made their way into the mainline.

Sorry if this has been covered before, but I am curious to know if
there is a good place or method to determine whether or not the
Cortex-A8 and A9 are still vulnerable and which versions or 4.4, 4.9,
or 4.14 have any items fixed.

Thanks for your patience.  :-)

adam

WARNING: multiple messages have this Message-ID (diff)
From: aford173@gmail.com (Adam Ford)
To: linux-arm-kernel@lists.infradead.org
Subject: Spectre and Cortex-A8/A9
Date: Wed, 9 May 2018 13:21:19 -0500	[thread overview]
Message-ID: <CAHCN7x+ghEW__YwgbXYO4g9HNKkwkQtXiswL1jihj0wwfKuR4Q@mail.gmail.com> (raw)

There is a lot of information pushed around the web about the Spectre
bug.  I went to ARM's support site and there are some patches
available from February that haven't made their way into the mainline.

Sorry if this has been covered before, but I am curious to know if
there is a good place or method to determine whether or not the
Cortex-A8 and A9 are still vulnerable and which versions or 4.4, 4.9,
or 4.14 have any items fixed.

Thanks for your patience.  :-)

adam

             reply	other threads:[~2018-05-09 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 18:21 Adam Ford [this message]
2018-05-09 18:21 ` Spectre and Cortex-A8/A9 Adam Ford
2018-05-10 14:47 ` Tony Lindgren
2018-05-10 14:47   ` Tony Lindgren

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=CAHCN7x+ghEW__YwgbXYO4g9HNKkwkQtXiswL1jihj0wwfKuR4Q@mail.gmail.com \
    --to=aford173@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.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.