xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xenbegn developer <xen.begn.dev@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [Query] Flow of PCI device dedicated to a domU
Date: Thu, 17 Jul 2014 10:42:23 +0100	[thread overview]
Message-ID: <53C79A7F.40304@citrix.com> (raw)
In-Reply-To: <CABJY2XAf-fVuzkmeZmMV_P_A7+e0XqPTBD++K+kMoEstRwqmrA@mail.gmail.com>

On 17/07/14 07:34, Xenbegn developer wrote:
> On 7/16/14, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> On 16/07/14 07:12, Xenbegn developer wrote:
>>> Hi,
>>> I am trying to understand the flow of how a PCI device driver in domU
>>> works after a PCI device is is assigned to a domU.
>>>
>>> a) If a PCI device is assigned to a domU, this device has to be on a
>>> PCI bus. So as per my view xen would have to somehow provide a PCI
>>> Controller on which this device is attached.
>>> => Is my assumption correct ? If yes how it is done, No then also How
>>> enumeration of this device happens in domU kernel
>> No.
>>
>> PV guests have no PCI root ports/bridges; they use devices as single
>> entities knowing that Xen/dom0 takes care of the other bits. HVM guests
>> have their PCI devices attached to the virtual southbridge which is all
>> emulated by Qemu.
>>
> How would a then a PV guest know about existence of a PCI device if it
> does not enumerate. Can you please elaborate on this.

The pcifront driver is capable of finding any PCI devices offered by
pciback in dom0.  It is all paravirtualised, and doesn't need explicit
hardware probing.

~Andrew

  reply	other threads:[~2014-07-17  9:42 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 [this message]
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
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=53C79A7F.40304@citrix.com \
    --to=andrew.cooper3@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 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).