On Tue, Oct 18, 2016 at 06:28:26PM +0200, Laurent Vivier wrote:
>
>
> On 18/10/2016 17:14, Laurent Vivier wrote:
> >
> >
> > On 18/10/2016 12:52, David Gibson wrote:
> >> tco_test uses the libqos PCI code to access the device. This makes perfect
> >> sense for the PCI config space accesses. H
On Tue, Oct 18, 2016 at 05:14:04PM +0200, Laurent Vivier wrote:
>
>
> On 18/10/2016 12:52, David Gibson wrote:
> > tco_test uses the libqos PCI code to access the device. This makes perfect
> > sense for the PCI config space accesses. However for IO, rather than the
> > usual PCI approach of ma
On 18/10/2016 17:14, Laurent Vivier wrote:
>
>
> On 18/10/2016 12:52, David Gibson wrote:
>> tco_test uses the libqos PCI code to access the device. This makes perfect
>> sense for the PCI config space accesses. However for IO, rather than the
>> usual PCI approach of mapping a PCI BAR, then
On 18/10/2016 12:52, David Gibson wrote:
> tco_test uses the libqos PCI code to access the device. This makes perfect
> sense for the PCI config space accesses. However for IO, rather than the
> usual PCI approach of mapping a PCI BAR, then accessing that, it instead
> uses the legacy approach
tco_test uses the libqos PCI code to access the device. This makes perfect
sense for the PCI config space accesses. However for IO, rather than the
usual PCI approach of mapping a PCI BAR, then accessing that, it instead
uses the legacy approach of fixed, known addresses in PCI IO space.
That do
