|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v11 1/3] iommu VT-d: separate rmrr addition function
>>> On 22.10.15 at 19:13, <elena.ufimtseva@xxxxxxxxxx> wrote:
> --- a/xen/drivers/passthrough/vtd/dmar.c
> +++ b/xen/drivers/passthrough/vtd/dmar.c
> @@ -583,6 +583,68 @@ out:
> return ret;
> }
>
> +static int register_one_rmrr(struct acpi_rmrr_unit *rmrru)
> +{
> + bool_t ignore = 0;
> + unsigned int i = 0;
> + int ret = 0;
> +
> + /* Skip checking if segment is not accessible yet. */
> + if ( !pci_known_segment(rmrru->segment) )
> + i = UINT_MAX;
> +
> + for ( ; i < rmrru->scope.devices_cnt; i++ )
> + {
> + u8 b = PCI_BUS(rmrru->scope.devices[i]);
> + u8 d = PCI_SLOT(rmrru->scope.devices[i]);
> + u8 f = PCI_FUNC(rmrru->scope.devices[i]);
> +
> + if ( pci_device_detect(rmrru->segment, b, d, f) == 0 )
> + {
> + dprintk(XENLOG_WARNING VTDPREFIX,
> + " Non-existent device (%04x:%02x:%02x.%u) is reported"
> + " in RMRR (%"PRIx64", %"PRIx64")'s scope!\n",
> + rmrru->segment, b, d, f,
> + rmrru->base_address, rmrru->end_address);
> + ignore = 1;
> + }
> + else
> + {
> + ignore = 0;
> + break;
> + }
> + }
> +
> + if ( ignore )
> + {
> + dprintk(XENLOG_WARNING VTDPREFIX,
> + " Ignore the RMRR (%"PRIx64", %"PRIx64") due to "
> + "devices under its scope are not PCI discoverable!\n",
> + rmrru->base_address, rmrru->end_address);
Broken indentation, but since everything else looks okay this can of
course be fixed up while committing, provided we can get a VT-d
maintainer ack.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |