From: Wei Liu <liuw@liuw.name>
To: Eric Camachat <eric.camachat@gmail.com>
Cc: xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: mmap in PV xen-4.0.1
Date: Fri, 12 Aug 2011 12:26:08 +0800 [thread overview]
Message-ID: <20110812042608.GA2760@limbo> (raw)
In-Reply-To: <CACeEFf7X1cCwPxDfaCGuUGF0qTnrBO_jnMa_UNd_Ni2=AosAoA@mail.gmail.com>
On Thu, Aug 11, 2011 at 10:11:20AM -0700, Eric Camachat wrote:
>
> Let us back to my original concern:
> Why remap_pfn_range() woks with my own device node, but deesn't work
> with /dev/mem node?
> This behavior is confused me.
>
> /Eric
Well, I slightly modify your code -- remove the ioctl and hardcoded
*base into mapper, and run on my box in dom0 (Xen 4.2 + 2.6.39 PVOPS),
I get following output and kernel log:
paddr = 0x6d368000
mem = 0xffffffffffffffff
map = 0x7fa928e88000
map[0]= 1234
map[1]= abcd
[ 405.039120] memtest: registering /dev/memtest (886)
[ 405.039125] memtest: size of phys_addr_t is 8 bytes
[ 405.039132] memtest: _vbase = 0xffff88006d368000
[ 405.039134] memtest: _pbase = 0x6d368000
[ 405.039135] memtest: _mbase = 0x6fbaa000
[ 781.414747] Program mapper tried to access /dev/mem between 6d368000->6d36c000.
[ 781.414764] memtest_vma_open: virt 0x7f327a275000, phys 0x6d368000
[ 781.414942] mapper[2744]: segfault at ffffffffffffffff ip 00000000004008d7 sp 00007fff233638e0 error 4 in mapper[400000+1000]
[ 781.415064] memtest_vma_close
[ 891.350796] Program mapper tried to access /dev/mem between 6d368000->6d36c000.
[ 891.350813] memtest_vma_open: virt 0x7fa928e88000, phys 0x6d368000
[ 891.350987] mapper[2811]: segfault at ffffffffffffffff ip 00000000004008d7 sp 00007fffc154efd0 error 4 in mapper[400000+1000]
[ 891.351102] memtest_vma_close
Looking into the kernel source, a check in range_is_allowed failed so
I just can't map /dev/mem with specified range (-EPERM).
But please note that my output of map[0] and map[1] are correct, while
your output is not correct ('4C4C4C4C'), which you ignored
previously. Why not make sure your mapper works correctly? Or can you
try newer kernel and Xen?
Wei.
next prev parent reply other threads:[~2011-08-12 4:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACeEFf77eOLLNgsJwEYdzeiuxm+qDcO2zs09FK-Waas0sxcwLQ@mail.gmail.com>
2011-08-10 6:29 ` mmap in PV xen-4.0.1 Eric Camachat
2011-08-10 9:12 ` Wei Liu
2011-08-10 17:14 ` Ranjith Ravi
2011-08-10 17:50 ` Konrad Rzeszutek Wilk
2011-08-10 18:31 ` Eric Camachat
2011-08-10 19:25 ` Konrad Rzeszutek Wilk
2011-08-10 19:42 ` Ian Campbell
2011-08-10 19:45 ` Eric Camachat
2011-08-10 20:59 ` BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0] Mark Schneider
2011-08-13 15:15 ` Konrad Rzeszutek Wilk
2011-08-10 19:45 ` mmap in PV xen-4.0.1 Eric Camachat
2011-08-11 1:31 ` Wei Liu
2011-08-11 3:10 ` Eric Camachat
2011-08-11 17:11 ` Eric Camachat
2011-08-12 4:26 ` Wei Liu [this message]
2011-08-12 17:20 ` Eric Camachat
2011-08-16 3:13 ` Ranjith Ravi
2011-08-16 5:06 ` Konrad Rzeszutek Wilk
2011-08-16 18:27 ` Ranjith Ravi
2011-08-17 2:20 ` Konrad Rzeszutek Wilk
2011-08-11 0:33 ` Eric Camachat
2011-08-11 1:21 ` Wei Liu
2011-08-11 1:29 ` Eric Camachat
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=20110812042608.GA2760@limbo \
--to=liuw@liuw.name \
--cc=eric.camachat@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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).