On Thu, Jul 25, 2019 at 08:00:23AM -0600, Alex Williamson wrote:
> On Thu, 25 Jul 2019 06:43:04 -0400
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Jul 25, 2019 at 02:37:33PM +0800, Peter Xu wrote:
> > > After re-read Michael's reply, I feel like what Michael suggested is
> > > that we can simply
On 7/24/19 2:42 PM, Alex Williamson wrote:
> On Wed, 24 Jul 2019 08:43:55 -0600
> Alex Williamson wrote:
>
>> On Wed, 24 Jul 2019 18:03:31 +0800
>> Peter Xu wrote:
>>
>>> On Wed, Jul 24, 2019 at 05:39:22AM -0400, Michael S. Tsirkin wrote:
On Wed, Jul 24, 2019 at 03:14:39PM +0800, Peter
On Thu, 25 Jul 2019 06:43:04 -0400
"Michael S. Tsirkin" wrote:
> On Thu, Jul 25, 2019 at 02:37:33PM +0800, Peter Xu wrote:
> > After re-read Michael's reply, I feel like what Michael suggested is
> > that we can simply ignore the bus-number-change case by the guest OS
> > for now, but I might be
On Thu, Jul 25, 2019 at 02:37:33PM +0800, Peter Xu wrote:
> After re-read Michael's reply, I feel like what Michael suggested is
> that we can simply ignore the bus-number-change case by the guest OS
> for now, but I might be wrong.
That's what I suggested, yes.
On Wed, Jul 24, 2019 at 08:43:55AM -0600, Alex Williamson wrote:
> On Wed, 24 Jul 2019 18:03:31 +0800
> Peter Xu wrote:
>
> > On Wed, Jul 24, 2019 at 05:39:22AM -0400, Michael S. Tsirkin wrote:
> > > On Wed, Jul 24, 2019 at 03:14:39PM +0800, Peter Xu wrote:
> > > > On Tue, Jul 23, 2019 at
On Wed, 24 Jul 2019 08:43:55 -0600
Alex Williamson wrote:
> On Wed, 24 Jul 2019 18:03:31 +0800
> Peter Xu wrote:
>
> > On Wed, Jul 24, 2019 at 05:39:22AM -0400, Michael S. Tsirkin wrote:
> > > On Wed, Jul 24, 2019 at 03:14:39PM +0800, Peter Xu wrote:
> > > > On Tue, Jul 23, 2019 at
On Wed, 24 Jul 2019 18:03:31 +0800
Peter Xu wrote:
> On Wed, Jul 24, 2019 at 05:39:22AM -0400, Michael S. Tsirkin wrote:
> > On Wed, Jul 24, 2019 at 03:14:39PM +0800, Peter Xu wrote:
> > > On Tue, Jul 23, 2019 at 11:26:18AM -0600, Alex Williamson wrote:
> > > > > On 3/29/19 11:49 AM, Alex
On Wed, Jul 24, 2019 at 05:39:22AM -0400, Michael S. Tsirkin wrote:
> On Wed, Jul 24, 2019 at 03:14:39PM +0800, Peter Xu wrote:
> > On Tue, Jul 23, 2019 at 11:26:18AM -0600, Alex Williamson wrote:
> > > > On 3/29/19 11:49 AM, Alex Williamson wrote:
> > > > > [Cc +Brijesh]
> > > > >
> > > > > Hi
On Wed, Jul 24, 2019 at 03:14:39PM +0800, Peter Xu wrote:
> On Tue, Jul 23, 2019 at 11:26:18AM -0600, Alex Williamson wrote:
> > > On 3/29/19 11:49 AM, Alex Williamson wrote:
> > > > [Cc +Brijesh]
> > > >
> > > > Hi Brijesh, will the change below require the IVRS to be updated to
> > > > include
On Tue, Jul 23, 2019 at 11:26:18AM -0600, Alex Williamson wrote:
> > On 3/29/19 11:49 AM, Alex Williamson wrote:
> > > [Cc +Brijesh]
> > >
> > > Hi Brijesh, will the change below require the IVRS to be updated to
> > > include aliases for all BDF ranges behind a conventional bridge? I
> > >
On Tue, Jul 23, 2019 at 11:26:18AM -0600, Alex Williamson wrote:
> On Mon, 1 Apr 2019 13:41:39 +
> "Singh, Brijesh" wrote:
>
> > Thanks for adding Alex.
> >
> > Adding Suravee.
> >
> >
> > On 3/29/19 11:49 AM, Alex Williamson wrote:
> > > [Cc +Brijesh]
> > >
> > > Hi Brijesh, will the
On Mon, 1 Apr 2019 13:41:39 +
"Singh, Brijesh" wrote:
> Thanks for adding Alex.
>
> Adding Suravee.
>
>
> On 3/29/19 11:49 AM, Alex Williamson wrote:
> > [Cc +Brijesh]
> >
> > Hi Brijesh, will the change below require the IVRS to be updated to
> > include aliases for all BDF ranges
Thanks for adding Alex.
Adding Suravee.
On 3/29/19 11:49 AM, Alex Williamson wrote:
> [Cc +Brijesh]
>
> Hi Brijesh, will the change below require the IVRS to be updated to
> include aliases for all BDF ranges behind a conventional bridge? I
> think the Linux code handles this regardless of
[Cc +Brijesh]
Hi Brijesh, will the change below require the IVRS to be updated to
include aliases for all BDF ranges behind a conventional bridge? I
think the Linux code handles this regardless of the firmware provided
aliases, but is it required per spec for the ACPI tables to include
bridge
On 28/03/2019 12:53, Auger Eric wrote:
Hi Robin,
On 3/28/19 11:56 AM, Robin Murphy wrote:
On 28/03/2019 10:38, Auger Eric wrote:
Hi Alex,
[+ Robin]
On 3/27/19 5:37 PM, Alex Williamson wrote:
On Wed, 27 Mar 2019 14:25:00 +0800
Peter Xu wrote:
On Tue, Mar 26, 2019 at 04:55:19PM -0600,
On 28/03/2019 10:38, Auger Eric wrote:
Hi Alex,
[+ Robin]
On 3/27/19 5:37 PM, Alex Williamson wrote:
On Wed, 27 Mar 2019 14:25:00 +0800
Peter Xu wrote:
On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
Conventional PCI buses pre-date requester IDs. An IOMMU cannot
Hi Robin,
On 3/28/19 11:56 AM, Robin Murphy wrote:
> On 28/03/2019 10:38, Auger Eric wrote:
>> Hi Alex,
>>
>> [+ Robin]
>>
>> On 3/27/19 5:37 PM, Alex Williamson wrote:
>>> On Wed, 27 Mar 2019 14:25:00 +0800
>>> Peter Xu wrote:
>>>
On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson
Hi Alex,
[+ Robin]
On 3/27/19 5:37 PM, Alex Williamson wrote:
> On Wed, 27 Mar 2019 14:25:00 +0800
> Peter Xu wrote:
>
>> On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
>>> Conventional PCI buses pre-date requester IDs. An IOMMU cannot
>>> distinguish by devfn & bus between
On Wed, Mar 27, 2019 at 11:35:35AM -0400, Michael S. Tsirkin wrote:
> On Wed, Mar 27, 2019 at 02:25:00PM +0800, Peter Xu wrote:
> > On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
> > > Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> > > distinguish by devfn &
On Wed, Mar 27, 2019 at 10:37:09AM -0600, Alex Williamson wrote:
> On Wed, 27 Mar 2019 14:25:00 +0800
> Peter Xu wrote:
>
> > On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
> > > Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> > > distinguish by devfn & bus
On Wed, 27 Mar 2019 19:07:44 +0100
Auger Eric wrote:
> Hi Alex,
>
> On 3/27/19 7:02 PM, Alex Williamson wrote:
> > On Wed, 27 Mar 2019 12:46:41 +0100
> > Auger Eric wrote:
> >
> >> Hi Alex,
> >>
> >> On 3/26/19 11:55 PM, Alex Williamson wrote:
> >>> Conventional PCI buses pre-date
On Wed, 27 Mar 2019 12:46:41 +0100
Auger Eric wrote:
> Hi Alex,
>
> On 3/26/19 11:55 PM, Alex Williamson wrote:
> > Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> > distinguish by devfn & bus between devices in a conventional PCI
> > topology and therefore we cannot assign
Hi Alex,
On 3/27/19 7:02 PM, Alex Williamson wrote:
> On Wed, 27 Mar 2019 12:46:41 +0100
> Auger Eric wrote:
>
>> Hi Alex,
>>
>> On 3/26/19 11:55 PM, Alex Williamson wrote:
>>> Conventional PCI buses pre-date requester IDs. An IOMMU cannot
>>> distinguish by devfn & bus between devices in a
On Wed, 27 Mar 2019 17:43:45 +0100
Auger Eric wrote:
> Hi,
>
> On 3/27/19 4:32 PM, Michael S. Tsirkin wrote:
> > On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
> >> Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> >> distinguish by devfn & bus between
On Wed, 27 Mar 2019 11:32:55 -0400
"Michael S. Tsirkin" wrote:
> On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
> > Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> > distinguish by devfn & bus between devices in a conventional PCI
> > topology and therefore we
On Wed, Mar 27, 2019 at 05:43:45PM +0100, Auger Eric wrote:
> Hi,
>
> On 3/27/19 4:32 PM, Michael S. Tsirkin wrote:
> > On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
> >> Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> >> distinguish by devfn & bus between
Hi,
On 3/27/19 4:32 PM, Michael S. Tsirkin wrote:
> On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
>> Conventional PCI buses pre-date requester IDs. An IOMMU cannot
>> distinguish by devfn & bus between devices in a conventional PCI
>> topology and therefore we cannot assign
On Wed, 27 Mar 2019 14:25:00 +0800
Peter Xu wrote:
> On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
> > Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> > distinguish by devfn & bus between devices in a conventional PCI
> > topology and therefore we cannot
On Wed, Mar 27, 2019 at 02:25:00PM +0800, Peter Xu wrote:
> On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
> > Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> > distinguish by devfn & bus between devices in a conventional PCI
> > topology and therefore we cannot
On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
> Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> distinguish by devfn & bus between devices in a conventional PCI
> topology and therefore we cannot assign them separate AddressSpaces.
> By taking this requester ID
Hi Alex,
On 3/26/19 11:55 PM, Alex Williamson wrote:
> Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> distinguish by devfn & bus between devices in a conventional PCI
> topology and therefore we cannot assign them separate AddressSpaces.
> By taking this requester ID aliasing
On Tue, Mar 26, 2019 at 04:55:19PM -0600, Alex Williamson wrote:
> Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> distinguish by devfn & bus between devices in a conventional PCI
> topology and therefore we cannot assign them separate AddressSpaces.
> By taking this requester ID
Conventional PCI buses pre-date requester IDs. An IOMMU cannot
distinguish by devfn & bus between devices in a conventional PCI
topology and therefore we cannot assign them separate AddressSpaces.
By taking this requester ID aliasing into account, QEMU better matches
the bare metal behavior and
33 matches
Mail list logo
