Prev: [PATCH 6/9] jump label: move ftrace_dyn_arch_init to common code
Next: viafb: complete support for VX800/VX855 accelerated framebuffer
From: Chris Wright on 9 Apr 2010 16:10
* Tom Lyon (pugs(a)lyon-about.com) wrote:
> On Friday 09 April 2010 02:58:19 am Avi Kivity wrote:
> > - access to all config space, but BARs must be translated so userspace
> > cannot attack the host
> Please elaborate. All of PCI config? All of PCIe config? Seems like a huge mess.

All of config space, but not raw access to all bits. So the MSI/MSI-X
capability writes need to be intermediated. There's bits in the
header too. And it's not just PCI, it's extended config space as well,
drivers may care about finding their whizzybang PCIe capability and doing
someting with it (and worse...they are allowed to put device specific
registers there, and worse yet...they do!).

thanks,
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 6/9] jump label: move ftrace_dyn_arch_init to common code
Next: viafb: complete support for VX800/VX855 accelerated framebuffer