|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [PATCH 2/2] vpci: use named rangeset for BARs
From: Oleksandr Andrushchenko <oleksandr_andrushchenko@xxxxxxxx>
Use a named range set instead of an anonymous one, but do not print it
while dumping range sets for a domain.
Suggested-by: Jan Beulich <jbeulich@xxxxxxxx>
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@xxxxxxxx>
---
xen/drivers/vpci/header.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/xen/drivers/vpci/header.c b/xen/drivers/vpci/header.c
index 40ff79c33f8f..82a3e50d6053 100644
--- a/xen/drivers/vpci/header.c
+++ b/xen/drivers/vpci/header.c
@@ -206,12 +206,16 @@ static void defer_map(struct domain *d, struct pci_dev
*pdev,
static int modify_bars(const struct pci_dev *pdev, uint16_t cmd, bool rom_only)
{
struct vpci_header *header = &pdev->vpci->header;
- struct rangeset *mem = rangeset_new(NULL, NULL, 0);
+ struct rangeset *mem;
+ char str[32];
struct pci_dev *tmp, *dev = NULL;
const struct vpci_msix *msix = pdev->vpci->msix;
unsigned int i;
int rc;
+ snprintf(str, sizeof(str), "%pp", &pdev->sbdf);
+ mem = rangeset_new(NULL, str, RANGESETF_no_print);
+
if ( !mem )
return -ENOMEM;
--
2.25.1
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |