mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kenneth R. Crudup" <kenny@panix.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Commit 25f12ae45fc1 ("maccess: rename probe_kernel_address to get_kernel_nofault") causing several OOPSes
Date: Sun, 21 Jun 2020 12:29:56 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2006211226240.9484@xps-7390> (raw)
In-Reply-To: <CAHk-=whj7YBvNT3FPHc8oUqwRhjbRkJESnUx6bbpA5ys6W9ujw@mail.gmail.com>


On Sat, Jun 20, 2020 at 6:46 AM Kenneth R. Crudup <kenny@panix.com> wrote:

> > So, be totally surprised :) I've just booted with "maccess: rename
> > probe_kernel_address to get_kernel_nofault" intact and your probe_roms.c
> > patch with no issues.
> > (Perhaps there's some sort of compiler optimization going on?)

On Sat, 20 Jun 2020, Linus Torvalds wrote:


> I'm staring at that opatch and not seeing how it could _possibly_ make
> any difference in code generation.

> Which is the obvious next step: would you mind compiling that file
> with and without the patch and sending me the two object files?

It looks like you had already, do you still need me to do this?

FWIW, here's my gcc info:

$  gcc --version
gcc (Ubuntu 9.3.0-13ubuntu1) 9.3.0

OH- I did change arch/x86/Makefile in my own builds- maybe this could matter?
Doubtful, but I could test later tonight or tomorrow (gotta do some ;l work in the
meantime).

----
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index 00e378de8bc0..37aff76f3067 100644
--- a/arch/x86/Makefile
+++ b/arch/x86/Makefile
@@ -123,7 +123,8 @@ else
         cflags-$(CONFIG_MPSC) += $(call cc-option,-march=nocona)

         cflags-$(CONFIG_MCORE2) += \
-                $(call cc-option,-march=core2,$(call cc-option,-mtune=generic))
+                $(call cc-option,-march=icelake-client,$(call cc-option,-mtune=native)) \
+                $(call cc-option,-mtune=icelake-client,$(call cc-option,-mtune=native))
        cflags-$(CONFIG_MATOM) += $(call cc-option,-march=atom) \
                $(call cc-option,-mtune=atom,$(call cc-option,-mtune=generic))
         cflags-$(CONFIG_GENERIC_CPU) += $(call cc-option,-mtune=generic)
----

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Orange County CA

  parent reply	other threads:[~2020-06-21 19:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.22.394.2006181751270.9276@xps-7390>
2020-06-19  6:50 ` Christoph Hellwig
2020-06-19  6:57   ` Kenneth R. Crudup
2020-06-19  7:42     ` Christoph Hellwig
2020-06-19  7:45       ` Kenneth R. Crudup
2020-06-20 13:46       ` Kenneth R. Crudup
2020-06-20 16:49         ` Linus Torvalds
2020-06-20 17:50           ` Linus Torvalds
2020-06-21 19:33             ` Kenneth R. Crudup
2020-06-21 19:29           ` Kenneth R. Crudup [this message]
2020-06-21 19:44             ` Linus Torvalds
2020-06-26  8:36               ` Kenneth R. Crudup

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=alpine.DEB.2.22.394.2006211226240.9484@xps-7390 \
    --to=kenny@panix.com \
    --cc=hch@lst.de \
    --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 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®