From: Andrea Arcangeli <aarcange@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sergio Gelato <Sergio.Gelato@astro.su.se>,
xen-devel@lists.xensource.com, 676360@bugs.debian.org
Subject: Re: xen: oops at atomic64_read_cx8+0x4
Date: Thu, 7 Jun 2012 18:17:04 +0200 [thread overview]
Message-ID: <20120607161704.GE21339@redhat.com> (raw)
In-Reply-To: <20120607155647.GO9472@phenom.dumpdata.com>
Hi,
On Thu, Jun 07, 2012 at 11:56:47AM -0400, Konrad Rzeszutek Wilk wrote:
> then the high part. Why that would trip the hypervisor
> is not clear to me. Perhaps in the past it only read the
That is the CONFIG_TRANSPARENT_HUGEPAGE=n case and in fact it doesn't
trip the hypervisor. That was tested too, it should work fine.
The problem is with the atomic64_read version, that one uses cmpxchg8b
to read the contents of the pmdp.
> Ah, by just skipping the thing if the low bits are zero.
Yep.
> didn't like somebody reading the high and low bit, but isn't the
> pmdval_t still 64-bit ? So I would have thought this would
The pmd format is unchanged, that's hardware.
> The thing is that I did install a 32-bit PAE guest (a Fedora) on a Fedora
> 17 dom0. So it looks like this is reading high part is fixed on the newer
> hypervisors, but now with the older ones. And the older one is Amazon EC2
> so some .. hack to workaround older hypervisors could be added.
The insn oopsing is cmpxchg8b and it's not reading the low/high part
in two separate insn but reading it in a single insn, which means the
kernel oopsing was built with CONFIG_TRANSPARENT_HUGEPAGE=y.
next prev parent reply other threads:[~2012-06-07 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120606132012.GB24320@hanuman.astro.su.se>
[not found] ` <20120606163000.GD9354@burratino>
[not found] ` <20120607064017.GA2112@hanuman.astro.su.se>
2012-06-07 7:33 ` xen: oops at atomic64_read_cx8+0x4 Jonathan Nieder
2012-06-07 10:33 ` Andrea Arcangeli
2012-06-07 12:30 ` Bug#676360: " Sergio Gelato
2012-06-07 15:56 ` Bug#676360: [Xen-devel] " Konrad Rzeszutek Wilk
2012-06-07 16:17 ` Andrea Arcangeli [this message]
2012-06-07 19:50 ` Jan Beulich
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=20120607161704.GE21339@redhat.com \
--to=aarcange@redhat.com \
--cc=676360@bugs.debian.org \
--cc=Sergio.Gelato@astro.su.se \
--cc=akpm@linux-foundation.org \
--cc=jrnieder@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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.