From: "Mihai Donțu" <mihai.dontu@gmail.com>
To: Tomasz Wroblewski <tomasz.wroblewski@citrix.com>
Cc: xen-devel@lists.xen.org, Razvan Cojocaru <rzvncj@gmail.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Why does xc_map_foreign_range() refuse to map pfns below 1M from a domU
Date: Wed, 4 Dec 2013 18:15:34 +0200 [thread overview]
Message-ID: <20131204181534.40e30ae3@mdontu-l> (raw)
In-Reply-To: <529F3A0A.9010602@citrix.com>
On Wed, 4 Dec 2013 15:19:54 +0100 Tomasz Wroblewski wrote:
> > Razvan and I are working together to find a solution to this. I took
> > your patch for a spin and while that code path is taken when
> > invoking xc_map_foreign_range(), the call still fails with EINVAL.
> > I haven't yet determined if the call stops in the domU kernel or it
> > reaches xen and gets terminated there. I've tried this on Ubuntu's
> > 3.8. on top of XenServer's xen-4.3.1.
> >
>
> Not sure why the patch doesn't work for you (you applied it to domU
> kernel which ties to map, right?), but before we applied this, the
> EINVAL was coming from hypervisor's HYPERVISOR_mmu_update in
> xen_remap_domain_mfn_range(), since the PTE constructed by
> xen_make_pte was invalid for the other domain.
> > Thanks,
> >
>
I'm sorry, I take back what I said before. The patch works OK, I just
interpreted the results wrong (some pages really _are_ unaccessible,
even from dom0). Thank you for all your help. :-)
--
Mihai Donțu
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-12-04 16:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 15:06 Why does xc_map_foreign_range() refuse to map pfns below 1M from a domU Razvan Cojocaru
2013-12-03 15:51 ` Ian Campbell
2013-12-03 15:59 ` Razvan Cojocaru
2013-12-03 16:09 ` Ian Campbell
2013-12-03 17:36 ` Tomasz Wroblewski
2013-12-03 18:59 ` Razvan Cojocaru
2013-12-03 19:07 ` Konrad Rzeszutek Wilk
2013-12-04 10:24 ` Tomasz Wroblewski
2013-12-04 10:31 ` Jan Beulich
2013-12-04 10:39 ` Ian Campbell
2013-12-04 10:42 ` Jan Beulich
2013-12-04 10:45 ` Ian Campbell
2013-12-04 10:54 ` Jan Beulich
2013-12-04 11:04 ` Ian Campbell
2013-12-04 11:23 ` Tomasz Wroblewski
2013-12-04 11:36 ` Jan Beulich
2013-12-04 12:01 ` Tomasz Wroblewski
2013-12-04 12:14 ` Jan Beulich
2013-12-04 12:23 ` Ian Campbell
2013-12-04 12:39 ` Jan Beulich
2013-12-04 16:40 ` Konrad Rzeszutek Wilk
2013-12-04 17:16 ` Tomasz Wroblewski
2014-07-08 14:54 ` Mihai Donțu
2013-12-04 11:42 ` Mihai Donțu
2013-12-04 14:19 ` Tomasz Wroblewski
2013-12-04 16:15 ` Mihai Donțu [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-03 16:18 Razvan Cojocaru
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=20131204181534.40e30ae3@mdontu-l \
--to=mihai.dontu@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=rzvncj@gmail.com \
--cc=tomasz.wroblewski@citrix.com \
--cc=xen-devel@lists.xen.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.