From: Balbir Singh <bsingharora@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: kernel bug in "Drop WIMG in favour of new constants"?
Date: Thu, 16 Jun 2016 15:28:10 +1000 [thread overview]
Message-ID: <c4e18fda-f864-6d2a-5dea-ab1b7da990e2@gmail.com> (raw)
In-Reply-To: <20160616043340.GB22590@birch.djwong.org>
On 16/06/16 14:33, Darrick J. Wong wrote:
> Hi Aneesh,
>
> I noticed when trying out 4.7-rc3 on qemu-2.5 that the kernel no longer
> boots. 4.6 booted just fine, so I bisected the kernel to the commit
> 30bda41aba4efb2370c97e2cbe7385de93ccc372, which is "powerpc/mm: Drop WIMG in
> favour of new constants". The changelog suggests that the KVM changes need
> closer review, and here's an actual crash:
>
> (I can send libvirt's machine xml, .config, and full dmesg if that helps.)
>
> --Darrick
Looking at the address - 0xd000080080000010, looks like map_kernel_page followed
by a fault here did not do the right thing. This EA range belongs to the io_remap
range, IIUC. The only suspicious bits I could find are
+ /*
+ * if host is mapped cache inhibited, make sure hptel also have
+ * cache inhibited.
+ */
+ if (wimg & HPTE_R_W) /* FIXME!! is this ok for all guest. ? */
+ return false;
Aneesh also posted some changes to hpte_update and hpte_updatepp that might be
interesting
Balbir
prev parent reply other threads:[~2016-06-16 5:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 4:33 kernel bug in "Drop WIMG in favour of new constants"? Darrick J. Wong
2016-06-16 5:23 ` Michael Ellerman
2016-06-16 5:57 ` Darrick J. Wong
2016-06-16 10:07 ` Aneesh Kumar K.V
2016-06-16 10:46 ` Aneesh Kumar K.V
2016-06-16 10:52 ` Aneesh Kumar K.V
2016-06-16 12:05 ` Benjamin Herrenschmidt
2016-06-16 14:45 ` Aneesh Kumar K.V
2016-06-16 14:31 ` Aneesh Kumar K.V
2016-06-16 22:30 ` Benjamin Herrenschmidt
2016-06-17 1:49 ` Darrick J. Wong
2016-06-16 16:23 ` Darrick J. Wong
2016-06-16 5:28 ` Balbir Singh [this message]
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=c4e18fda-f864-6d2a-5dea-ab1b7da990e2@gmail.com \
--to=bsingharora@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=darrick.wong@oracle.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).