From: Thomas Gleixner <tglx@linutronix.de>
To: Jan Beulich <jbeulich@novell.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Andi Kleen <ak@suse.de>,
Takashi Iwai <tiwai@suse.de>, LKML <linux-kernel@vger.kernel.org>,
discuss@x86-64.org
Subject: Re: [discuss] 2.6.23-rc8-mm1, -rc7-mm1 kill audio on HP nx6325
Date: Wed, 26 Sep 2007 10:22:30 +0200 [thread overview]
Message-ID: <1190794950.23376.21.camel@chaos> (raw)
In-Reply-To: <46FA274B.76E4.0078.0@novell.com>
On Wed, 2007-09-26 at 08:32 +0100, Jan Beulich wrote:
> >ioremap_nocache() does __ioremap(..., _PAGE_PCD);, then __ioremap() does
> >ioremap_page_range(..., _PAGE_PCD | other_stuff) That's one.
> >
> >__ioremap() then does ioremap_change_attr(..., _PAGE_PCD);. That's two.
> >
> >So I _think_ we're setting _PAGE_PCD twice on those pte's? Unclear. The
> >implementation is rather different from i386, too.
> >
> >I dunno why __change_page_attr() failed though. Perhaps this, in
> >change_page_attr_addr():
> >
> > if (!kernel_map || pte_present(pfn_pte(0, prot))) {
> >
> >should be &&
>
> Definitely not, and this code has been that way for a while.
>
> I rather suspect this change
>
> - if (!kpte) return 0;
> + if (!kpte)
> + return -EINVAL;
>
> to be the reason for the failure (and I had already sent a comment to this
> respect to Andi upon his review request).
This change exposes the problem. The question is why we do not have a
page table entry for the address, which was mapped right before that.
tglx
prev parent reply other threads:[~2007-09-26 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200709251353.52723.rjw@sisk.pl>
2007-09-25 16:08 ` 2.6.23-rc8-mm1, -rc7-mm1 kill audio on HP nx6325 Andrew Morton
2007-09-26 7:32 ` [discuss] " Jan Beulich
2007-09-26 8:22 ` Thomas Gleixner [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=1190794950.23376.21.camel@chaos \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=discuss@x86-64.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tiwai@suse.de \
/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