All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Martin <furryfuttock@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Realtime access to PCI NIC
Date: Thu, 10 Jul 2014 08:47:24 +0100	[thread overview]
Message-ID: <11710529870.20140710084724@gmail.com> (raw)
In-Reply-To: <1404830785.24591.2.camel@kazak.uk.xensource.com>

Thanks Ian,

Tuesday, July 8, 2014, 3:46:25 PM, you wrote:


> Only PCI cfg reads/writes go via the backend, I think. Any MMIO space
> (i.e. described in the PCI BARS) can be directly mapped, likewise for
> the IO port spaces associated with the device.

> I think PCI cfg space is only generally used during probing/setup etc.
> Hopefully you don't need to poke it at runtime?

You have confirmed the conclusion that I was coming to!

> Right, VT-d allows the MMIO stuff to be mapped to an HVM guest (PV
> doesn't even need that), but unfortunately there are bits in the pci cfg
> space which even a guest with the device passed to it shouldn't be able
> to mess with (I don't know the details though).

Perfect.

-- 
Best regards,
 Simon                            mailto:furryfuttock@gmail.com

  reply	other threads:[~2014-07-10  7:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 11:13 Consuming PCI device in PV kernel Simon Martin
2014-07-03 18:09 ` Konrad Rzeszutek Wilk
2014-07-07  8:21   ` Simon Martin
2014-07-07 11:22     ` Simon Martin
2014-07-07 12:21       ` Realtime access to PCI NIC Simon Martin
2014-07-08 14:46         ` Ian Campbell
2014-07-10  7:47           ` Simon Martin [this message]
2014-07-08 15:01       ` Consuming PCI device in PV kernel Konrad Rzeszutek Wilk
2014-07-10  7:54         ` Simon Martin
2014-07-11 16:47           ` Dario Faggioli
2014-07-15  8:37             ` Simon Martin
2014-07-15 14:56               ` Konrad Rzeszutek Wilk
2014-07-18 14:37       ` Simon Martin
2014-07-18 19:09         ` Konrad Rzeszutek Wilk
2014-07-21 10:13           ` Simon Martin
2014-07-21 10:53             ` Ian Campbell
2014-07-25 12:56               ` Simon Martin
2014-07-25 13:10                 ` Ian Campbell
2014-07-25 13:21                   ` Simon Martin
2014-07-25 13:37                     ` Ian Campbell
2014-07-25 13:50                       ` Andrew Cooper
2014-07-25 14:20                         ` Simon Martin
2014-07-25 14:25                           ` Andrew Cooper
2014-07-25 14:30                             ` Simon Martin
2014-07-25 14:33                               ` Ian Campbell
2014-07-25 14:36                                 ` Simon Martin
2014-07-25 14:28                       ` Simon Martin

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=11710529870.20140710084724@gmail.com \
    --to=furryfuttock@gmail.com \
    --cc=Ian.Campbell@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.