From: Don Zickus <dzickus@redhat.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86,nmi: Fix section mismatch warnings on 32-bit
Date: Tue, 5 Jun 2012 14:35:39 -0400 [thread overview]
Message-ID: <20120605183539.GA32472@redhat.com> (raw)
In-Reply-To: <4FCE44FC0200007800088524@nat28.tlf.novell.com>
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
On Tue, Jun 05, 2012 at 04:42:20PM +0100, Jan Beulich wrote:
> >>> On 05.06.12 at 16:47, Don Zickus <dzickus@redhat.com> wrote:
> > On Tue, Jun 05, 2012 at 09:12:13AM +0100, Jan Beulich wrote:
> >> So before applying a change like this, I'd really like to understand
> >> the issue itself. Could you simply attach the nmi_selftest.o file
> >> that you get without your patch here (and indicate which
> >> upstream version or revision the corresponding source file was
> >> from, to be able to re-construct what the compiler actually did)?
> >
> > I could but it might be easier for you to re-create it on your end.
> > Using gcc-4.4.4 on an x86_64 box and v3.5-rc1, I just set
> > CONFIG_DEBUG_NMI_SELFTEST to 'y' and compile with
> >
> > make ARCH=i386 O=out/i686
> >
> > and it easily reproduces for me.
>
> I don't think I have a plain 4.4.4 around anywhere, nor is it clear
> whether you used a plain one (and how it was configured). For
> tricky, highly version dependent things like this (where a compiler
> bug also can't be excluded), having the _exact_ object file the
> problem was seen with would be much easier than trying to hunt
> down a compiler version that I can reproduce this with.
I didn't think it would be compiler dependent as I do not know what
compiler the reporter was using. I used a RHEL-6 4.4.4 compiler (which
you probably don't have :^) ).
I attached a gzip'd copy of my nmi_selftest.o file for your debugging.
Cheers,
Don
[-- Attachment #2: nmi_selftest.o.gz --]
[-- Type: application/x-gzip, Size: 16267 bytes --]
next prev parent reply other threads:[~2012-06-05 18:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 19:56 [PATCH] x86,nmi: Fix section mismatch warnings on 32-bit Don Zickus
2012-06-05 8:12 ` Jan Beulich
2012-06-05 14:47 ` Don Zickus
2012-06-05 15:42 ` Jan Beulich
2012-06-05 18:35 ` Don Zickus [this message]
2012-06-06 11:14 ` Jan Beulich
2012-06-06 14:03 ` Don Zickus
2012-06-06 15:45 ` Ingo Molnar
2012-06-06 18:28 ` Don Zickus
2012-06-07 7:43 ` Li Zhong
2012-06-07 12:48 ` Don Zickus
2012-06-08 20:51 ` Don Zickus
2012-06-11 1:36 ` Zhong Li
2012-06-11 8:19 ` Ingo Molnar
2012-06-05 16:13 ` Sam Ravnborg
2012-06-05 16:18 ` Jan Beulich
2012-06-05 17:22 ` Sam Ravnborg
2012-06-08 2:06 ` Don Zickus
2012-06-08 5:40 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2012-06-06 14:05 Don Zickus
2012-06-06 21:22 ` Witold Baryluk
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=20120605183539.GA32472@redhat.com \
--to=dzickus@redhat.com \
--cc=JBeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox