kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: getarunks@gmail.com (Arun Sudhilal)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Error reading /dev/mem
Date: Mon, 3 Oct 2016 18:30:26 +0530	[thread overview]
Message-ID: <CABOM9ZraVOOcyc2XDvkfho52sr37F-xnizTYxB6QDxDw1hnhWw@mail.gmail.com> (raw)
In-Reply-To: <CAOK12Db6OzJagTgXMNcpJFOSnvOqNL8RqH=5GUVoi66wn=rC_g@mail.gmail.com>

Hello Paddie,

On Wed, Sep 28, 2016 at 1:19 AM, Paddie O'Brien <paddieobrien@gmail.com> wrote:
> Hi,
>
> I have a system call that maps virtual to physical addresses. I have
> disabled CONFIG_STRICT_DEVMEM and am reading from /dev/mem to verify
> that the contents of the syscall-returned physical address match the
> contents of the virtual address. It works fine up to a point. Reading
> beyond byte 935321597 in /dev/mem throws a "bad address" error. Not
> sure it's relevant but I'm running on virtual box and specifying 1GB
> of RAM. Tried with 2GB of RAM and hit the same problem.
>
> Any idea why I can't read beyond the above point?

Can you send the output to cat /proc/iomem?

>
> Thanks.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      parent reply	other threads:[~2016-10-03 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 19:49 Error reading /dev/mem Paddie O'Brien
2016-10-01 17:45 ` Mulyadi Santosa
2016-10-03 10:00   ` Paddie O'Brien
2016-10-10  6:55     ` Mulyadi Santosa
2016-10-03 13:00 ` Arun Sudhilal [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=CABOM9ZraVOOcyc2XDvkfho52sr37F-xnizTYxB6QDxDw1hnhWw@mail.gmail.com \
    --to=getarunks@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).