mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel J Blueman" <daniel.blueman@gmail.com>
To: bhuvan.mittal@st.com
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: How to make mmap'ed kernel buffer non-cacheable
Date: Fri, 20 Apr 2007 14:32:41 +0100	[thread overview]
Message-ID: <6278d2220704200632p3300a6e2y8c9d14f4d735015c@mail.gmail.com> (raw)

On 20 Apr, 14:20, Bhuvan Kumar MITTAL <bhuvan.mit...@st.com> wrote:
> Hi,
>   I am working on an audio device driver development on Linux. I have a kernel
> buffer which I have mapped to user space using mmap call from user space. My
> problem is that the data which comes to the kernel buffer is getting dropped in
> user space and I get only 50-60% of the data which is randomly ordered. The user
> to kernel level buffer address translation code is fine and I suspect this data
> dropping is occurring coz the kernel buffer is cacheable. Please suggest me some
> way of making the entire buffer non cacheable. I am stuck on this for quite a while
> now.

You can use rdmsr() in your driver to check if the page attribute
table MSR is available, then find and/or add the right entry in the
table to set in each page's flags. This is documented in the Intel
IA-32 Intel Architecture Software Developer's Manuals at intel.com.

Dan
-- 
Daniel J Blueman

             reply	other threads:[~2007-04-20 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20 13:32 Daniel J Blueman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-20 13:00 Bhuvan Kumar MITTAL
2007-04-20 13:43 ` Alan Cox
2007-04-23  4:11   ` Bhuvan Kumar MITTAL
2007-04-23  4:25     ` Nick Piggin
2007-05-01  3:58       ` Bhuvan Kumar MITTAL
2007-05-01 12:09         ` Nick Piggin
2007-05-02  8:23           ` Bhuvan Kumar MITTAL
2007-05-02  8:45             ` Nick Piggin

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=6278d2220704200632p3300a6e2y8c9d14f4d735015c@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=bhuvan.mittal@st.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®