From: Simon Martin <furryfuttock@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Xenbegn developer <xen.begn.dev@gmail.com>,
ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: [Query] Flow of PCI device dedicated to a domU
Date: Tue, 22 Jul 2014 16:56:57 +0100 [thread overview]
Message-ID: <1721487090.20140722165657@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1407221453580.2295@kaball.uk.xensource.com>
Hello Stefano,
> The basic mechanism is that Xen assigns the PCI root complex/host
> bridge to Dom0. Dom0 walks the bus and finds out the devices available.
> When the user assigns a PCI device to a VM, the toolstack (xl/libxl)
> issues hypercalls to remap interrupts and MMIO regions of that device
> into the guest VM.
I am currently trying writing my own PCI front to access directly a
PCI device from my PV guest.
If I read this correctly you are saying that the MMIO region is
already mapped into my domain by xl? So when I go and read the BAR
register from the PCI configuration I can just go and access it
directly or do I have to update the VA mapping?
--
Best regards,
Simon mailto:furryfuttock@gmail.com
next prev parent reply other threads:[~2014-07-22 15:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 6:12 [Query] Flow of PCI device dedicated to a domU Xenbegn developer
2014-07-16 9:50 ` Andrew Cooper
2014-07-17 6:34 ` Xenbegn developer
2014-07-17 9:42 ` Andrew Cooper
2014-07-22 9:43 ` Xenbegn developer
2014-07-22 9:53 ` Andrew Cooper
2014-07-22 10:02 ` Xenbegn developer
2014-07-22 9:50 ` Xenbegn developer
2014-07-22 9:56 ` Andrew Cooper
2014-07-22 10:13 ` Xenbegn developer
2014-07-22 10:33 ` Andrew Cooper
2014-07-22 10:51 ` Xenbegn developer
2014-07-22 11:33 ` Xenbegn developer
2014-07-22 12:44 ` Ian Campbell
2014-07-22 14:11 ` Stefano Stabellini
2014-07-22 15:56 ` Simon Martin [this message]
2014-07-22 16:01 ` Simon Martin
2014-07-22 16:02 ` Ian Campbell
2014-07-22 16:06 ` Simon Martin
2014-07-22 16:06 ` Stefano Stabellini
2014-07-22 16:09 ` Simon Martin
2014-07-24 5:17 ` Xenbegn developer
2014-07-24 10:04 ` Stefano Stabellini
2014-07-24 8:08 ` Xenbegn developer
2014-07-24 9:20 ` Ian Campbell
2014-07-24 10:21 ` Stefano Stabellini
2014-07-16 13:46 ` Konrad Rzeszutek Wilk
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=1721487090.20140722165657@gmail.com \
--to=furryfuttock@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xen.begn.dev@gmail.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.