From: "Khandelwal, Shubham" <Shubham.Khandelwal@harman.com>
To: 'Ian Campbell' <Ian.Campbell@citrix.com>
Cc: Julien Grall <julien.grall@linaro.org>,
xen-devel <xen-devel@lists.xen.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Arianna Avanzini <avanzini.arianna@gmail.com>
Subject: Re: Device pass through on XEN on ARM
Date: Thu, 12 Jun 2014 10:36:15 +0200 [thread overview]
Message-ID: <3A6586556649FF42BA3240F179473FD114885FF8C5@HIKAWSEX01.ad.harman.com> (raw)
In-Reply-To: <1402479753.9727.6.camel@kazak.uk.xensource.com>
Hello Ian,
On 06/11/2014 03:13 PM, Ian Campbell wrote:
> > Just to try out the passthrough using the hacks you mentioned, I made
> > changes in xen to assign a GPIO controlled LED to domU by calling
> > map_mmio_regions() in the domain creation path. After domU boots, when
> > I try to access the LED using ioremap, ioread and iowrite from kernel
> > space I see that I am not able to control the LED,
> How does it fail? Does it give a fault in the hypervisor or the guest
> kernel or just silently eat the MMIO writes and not do anything?
There is a panic in the guest kernel
> 0x4xxxxxxx is a RAM region on 4.5 (see the end of
> xen/include/public/arch-arm.h), I suspect your mmio mapping is being
> clobbered by a RAM mapping (and therefore that your answer above is
> "silently does nothing".
I just checked xen/include/public/arch-arm.h Line 372 is
#define GUEST_RAM_BASE 0x80000000ULL
So as per my understanding 0x4xxxxxxx is not a ram region and thus there should not be any clobbering.
> Do you need this to be a 1:1 mapping or could you move it to some free
> space? Most of the low GB is free (but do check arch-arm.h) to be used
> for MMIO mappings.
I do not necessarily need it to be a 1:1 mapping.
> Ian.
Regards
Shubham Khandelwal
next prev parent reply other threads:[~2014-06-12 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 11:35 Device pass through on XEN on ARM Khandelwal, Shubham
2014-05-01 14:44 ` Julien Grall
2014-05-01 14:56 ` Ian Campbell
2014-06-11 9:16 ` Khandelwal, Shubham
2014-06-11 9:42 ` Ian Campbell
2014-06-11 9:53 ` Gordan Bobic
2014-06-11 10:00 ` Ian Campbell
2014-06-11 10:07 ` Gordan Bobic
2014-06-12 8:36 ` Khandelwal, Shubham [this message]
2014-06-12 8:49 ` Ian Campbell
2014-06-11 14:07 ` Dario Faggioli
[not found] ` <3A6586556649FF42BA3240F179473FD114885FF8B6@HIKAWSEX01.ad.harman.com>
2014-05-22 16:16 ` Julien Grall
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=3A6586556649FF42BA3240F179473FD114885FF8C5@HIKAWSEX01.ad.harman.com \
--to=shubham.khandelwal@harman.com \
--cc=Ian.Campbell@citrix.com \
--cc=avanzini.arianna@gmail.com \
--cc=julien.grall@linaro.org \
--cc=xen-devel@lists.xen.org \
--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 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.