From: "Hans J. Koch" <hjk@linutronix.de>
To: "Leon Woestenberg" <leon.woestenberg@gmail.com>
Cc: "Jean-Samuel Chenard" <jsamch@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>, "Greg KH" <greg@kroah.com>,
grant.likely@secretlab.ca,
"Juergen Beisert" <juergen127@kreuzholzen.de>
Subject: Re: Linux UIO driver cache problem in PowerPC (fix)
Date: Sun, 16 Mar 2008 13:20:08 +0100 [thread overview]
Message-ID: <20080316132008.5050153d@bluebox.local> (raw)
In-Reply-To: <c384c5ea0803151951g47bd5214j18334f03f95821fe@mail.gmail.com>
Am Sun, 16 Mar 2008 03:51:10 +0100
schrieb "Leon Woestenberg" <leon.woestenberg@gmail.com>:
> Hello,
>
> On Fri, Mar 14, 2008 at 11:33 AM, Hans J. Koch <hjk@linutronix.de>
> wrote:
> > I investigated a bit and found your patch to be correct. I cleaned
> > it up a bit and sent it to Greg and LKML. I added you as author
> > and also took the freedom to add your Signed-off-by.
> >
> Could you elaborate why exactly this is needed, maybe even as a
> comment in the patch?
As far as I understood, the VM_IO flag simply means that the page is
used for IO. On some architectures this automatically means that the
page is not cached, but this is not guaranteed. That's why
pgprot_noncached() exists.
If I misunderstood something or somebody can explain it better, please
let me know.
>
> It seemed non-trivial enough to rectify adding a comment.
It _is_ trivial. It's just something you don't need every day, and
therefore it's not known to everybody (including me) or not obvious.
But if you look at it:
VM_IO means IO
pgprot_noncached means noncached
What could be more trivial?
Thanks,
Hans
prev parent reply other threads:[~2008-03-16 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169c03cb0803121222h5fca9cdal5af873cd2a700f4d@mail.gmail.com>
2008-03-13 7:19 ` Linux UIO driver cache problem in PowerPC (fix) Hans-Jürgen Koch
2008-03-13 21:53 ` Grant Likely
2008-03-14 7:41 ` Juergen Beisert
2008-03-14 10:33 ` Hans J. Koch
2008-03-16 2:51 ` Leon Woestenberg
2008-03-16 12:20 ` Hans J. Koch [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=20080316132008.5050153d@bluebox.local \
--to=hjk@linutronix.de \
--cc=grant.likely@secretlab.ca \
--cc=greg@kroah.com \
--cc=jsamch@gmail.com \
--cc=juergen127@kreuzholzen.de \
--cc=leon.woestenberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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