From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Khandelwal, Shubham" <Shubham.Khandelwal@harman.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Arianna Avanzini <avanzini.arianna@gmail.com>,
Julien Grall <julien.grall@linaro.org>,
'Ian Campbell' <Ian.Campbell@citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: Device pass through on XEN on ARM
Date: Wed, 11 Jun 2014 16:07:37 +0200 [thread overview]
Message-ID: <1402495657.16827.99.camel@Solace> (raw)
In-Reply-To: <3A6586556649FF42BA3240F179473FD114885FF8C1@HIKAWSEX01.ad.harman.com>
[-- Attachment #1.1: Type: text/plain, Size: 2196 bytes --]
On mer, 2014-06-11 at 11:16 +0200, Khandelwal, Shubham wrote:
> On 05/01/2014 08:26 PM, Ian Campbell wrote:
> > Obviously this is all very hacky and as Julien says there are various
> > things in the pipeline for 4.5 which will allow this to be done
> > properly.
> >
> > Ian.
>
> Hello Ian, Julien,
>
> 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, also when I try to control LED using sysfs from user space it shows 'no such device' error.
>
> I am using xen 4.5 unstable and I have made the following changes in xen/common/domctl.c :: do_domctl(), after line 473:
>
>
>
> int passthrough = map_mmio_regions(d, 0x4805B000, 0x4805B000 + 0x1000, 0x4805B000);
> if (passthrough)
> printk("Failed to map passthrough_LED @ 0x4805B000 to dom%d\n", d->domain_id);
>
>
>
> While booting domU, in the logs I can see there is no error in map_mmio_regions(). Am I missing something here.
>
May I suggest trying to apply Arianna's series, and see whether that
helps? IIRC, there should even be the possibility of setting up non 1:1
mappings, directly from the config file (uless that got dropped in the
latest versions, which I could not follow closely).
In any case, it look like both less work, and a more tested path (given
the amount of attention and review the series is getting). It also would
be greeat to have some more testing of the series itself, not to mention
that, if it works, you'll be all set for when the series will go
upstream! :-P
I believe the last version of Arianna's series is this one:
http://markmail.org/thread/wtevxxizyxjhvmg2
Just 2 cents... :-)
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-06-11 14:07 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
2014-06-12 8:49 ` Ian Campbell
2014-06-11 14:07 ` Dario Faggioli [this message]
[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=1402495657.16827.99.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Shubham.Khandelwal@harman.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.