From: "H. Peter Anvin" <hpa@zytor.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Venkatesh Pallipadi <venki@google.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] x86, PAT: honor CONFIG_STRICT_DEVMEM if pat is disable]
Date: Fri, 22 Jul 2011 11:30:55 -0700 [thread overview]
Message-ID: <4E29C1DF.9080705@zytor.com> (raw)
In-Reply-To: <20110722173102.GA26935@tiehlicka.suse.cz>
On 07/22/2011 10:31 AM, Michal Hocko wrote:
>
> Thanks for the clarification!
> What do you think about fixing the nopat with STRICT_DEVMEM like the
> patch does?
>
>From what I gather from your patch, the issue is that STRICT_DEVMEM
isn't being honored with nopat? This is an obvious bug and should be fixed.
-hpa
next prev parent reply other threads:[~2011-07-22 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 9:11 [PATCH] x86, PAT: honor CONFIG_STRICT_DEVMEM if pat is disable] Michal Hocko
2011-07-22 16:15 ` H. Peter Anvin
2011-07-22 17:31 ` Michal Hocko
2011-07-22 18:30 ` H. Peter Anvin [this message]
2011-07-23 12:39 ` Michal Hocko
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=4E29C1DF.9080705@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mingo@elte.hu \
--cc=venki@google.com \
--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 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.