Hi Andre,
On 20/01/2017 17:05, Andre Przywara wrote:
On 20/01/17 12:18, Julien Grall wrote:
Hi Andre,
On 20/01/2017 12:27, Andre Przywara wrote:
On 20/01/17 11:12, Julien Grall wrote:
Hello,
On 04/01/2017 22:47, Stefano Stabellini wrote:
On Thu, 22 Dec 2016, Andre Przywara wrote:
Each
Hi,
On 20/01/17 12:18, Julien Grall wrote:
> Hi Andre,
>
> On 20/01/2017 12:27, Andre Przywara wrote:
>> On 20/01/17 11:12, Julien Grall wrote:
>>> Hello,
>>>
>>> On 04/01/2017 22:47, Stefano Stabellini wrote:
On Thu, 22 Dec 2016, Andre Przywara wrote:
> Each ITS maps a pair of a
Hi Andre,
On 20/01/2017 12:27, Andre Przywara wrote:
On 20/01/17 11:12, Julien Grall wrote:
Hello,
On 04/01/2017 22:47, Stefano Stabellini wrote:
On Thu, 22 Dec 2016, Andre Przywara wrote:
Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and
an EventID (the MSI payload or
Hi,
On 20/01/17 11:12, Julien Grall wrote:
> Hello,
>
> On 04/01/2017 22:47, Stefano Stabellini wrote:
>> On Thu, 22 Dec 2016, Andre Przywara wrote:
>>> Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and
>>> an EventID (the MSI payload or interrupt ID) to a pair of LPI number
Hello,
On 04/01/2017 22:47, Stefano Stabellini wrote:
On Thu, 22 Dec 2016, Andre Przywara wrote:
Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and
an EventID (the MSI payload or interrupt ID) to a pair of LPI number
and collection ID, which points to the target CPU.
This
Hi Stefano,
On 04/01/17 21:47, Stefano Stabellini wrote:
> On Thu, 22 Dec 2016, Andre Przywara wrote:
>> Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and
>> an EventID (the MSI payload or interrupt ID) to a pair of LPI number
>> and collection ID, which points to the target
On Thu, 22 Dec 2016, Andre Przywara wrote:
> Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and
> an EventID (the MSI payload or interrupt ID) to a pair of LPI number
> and collection ID, which points to the target CPU.
> This mapping is stored in the device and collection
Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and
an EventID (the MSI payload or interrupt ID) to a pair of LPI number
and collection ID, which points to the target CPU.
This mapping is stored in the device and collection tables, which software
has to provide for the ITS to
