[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2] vpci/header: cope with devices not having vpci allocated
- To: Jan Beulich <jbeulich@xxxxxxxx>
- From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Date: Mon, 29 May 2023 10:52:52 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=JlxRk83gRDW2cqGmDzUxNl8Bv4umjbDDyyOgrnw3Goo=; b=oCA/tbP2wuYbyHL3Gklq1OSp0FDquRwHWmsLdLanYou+xiRRpLKsPcDkwhJRdVmi+C2cl6M/GqLUg8kQFxQrxouPkoEfNrt3fTyY30pjOsussRfvX2IzdB/BXqHpc/Tw4NoqEbkYSJ4iiK94sWPPxz3biaWg3clnR8x9oHvPVm3OsK7yKEF5xDi8rCYnNJ5pfcHX08DIhKJIBS8tHbu+m9E0LNhEv3F6sDXJdD8YLNv0zCao0DiP/HQwdF1OirO3V0j1V+v0xT297XsdZc+pRUfcAG+4E+rKjc/5Xkb0Aax87uc40QCHCq9kG3N8FEkR9t47J/TD5Gadptmw3PD1og==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bnMj1rbF1HdlNpVldcjP0zKLuocujjQmrTWMgX5qsLRF9jfFSre9+etl4DpEztRd5QfzE1VpDuPy5e4gRalQzgZIdbpxg2FSwfCtwBpZ9N2jZIcqUPcuTVYTcRhCbCjVg/59BSnoXW0ow/RE0XiOpDelcemeOdkn07LnDlSeK1Z1fzEsrJO3iVuOA0qg1UHXuuSzJiCCPcI+CdmQBu6xfY8pm6ZuKpeVaQFWCScUe4ML12hSSaTCYWlKTMjBcWA7GH7+AmF3h4gMboofk9YbDcLRxEo4xgG6iSmcNtfaejGtCWxenkXvipPuVwt9uqPtmqzK1W21ZD61h0Gd6QvBcA==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
- Delivery-date: Mon, 29 May 2023 08:53:18 +0000
- Ironport-data: A9a23:flBzlK2btvjtRI4eT/bD5cFwkn2cJEfYwER7XKvMYLTBsI5bpzMGm mFNXj2Hb/qPZzD9etBzO4/l9U1U7JDcz9NrGwpppC1hF35El5HIVI+TRqvS04F+DeWYFR46s J9OAjXkBJppJpMJjk71atANlVEliefTAOK6ULWeUsxIbVcMYD87jh5+kPIOjIdtgNyoayuAo tq3qMDEULOf82cc3lk8teTb8HuDgNyo4GlD5gFkNagR1LPjvyJ94Kw3dPnZw0TQGuG4LsbiL 87fwbew+H/u/htFIrtJRZ6iLyXm6paLVeS/oiI+t5qK23CulQRrukoPD9IOaF8/ttm8t4sZJ OOhF3CHYVxB0qXkwIzxWvTDes10FfUuFLTveRBTvSEPpqFvnrSFL/hGVSkL0YMkFulfLEty0 f0hOjAxVRXfrrmU0vWKEMl2mZF2RCXrFNt3VnBI6xj8VK9jbbWdBqLA6JlfwSs6gd1IEbDGf c0FZDFzbRPGJRpSJlMQD5F4l+Ct7pX9W2QA9BTJ+uxqvC6Kkl0ZPLvFabI5fvSQQspYhACAr 3/u9GXlGBAKcteYzFJp91r137eWxXOhBdt6+LuQ+q9z3E/QzVQpFxxOd0alndeV1hDvcocKQ 6AT0m90xUQoz2SpRNTgWxyzoFafowURHdFXFoUS+AyLj6bZ/QudLmwFVSJaLswrstcsQj4n3 UPPmMnmbQGDq5WQQHOZs7uR8zW7PHFMKXdYPHFVCwwY/9PkvYc/yArVScpuG7K0iduzHizsx zeNr241gLB7YdM36phXNGvv21qEzqUlhCZsjukLdgpJNj9EWbM=
- Ironport-hdrordr: A9a23:L8G2rqMKNjMswsBcTnqjsMiBIKoaSvp037Dk7SFMoHtuA6qlfq GV7ZMmPHrP4gr5N0tMpTntAsW9qDbnhP1ICWd4B8bfYOCkghrUEGlahbGSvAEIYheOiNK1t5 0BT0EOMqyVMbEgt7eC3ODQKb9Jq+VvsprY59s2qU0DcegAUdAE0+4WMGim+2RNNXh7LKt8Op qAx9ZN4wGtcW4Qaa2AdwM4dtmGid3XtY7sJSULDR4/6AWIkFqTmcXHOind8BcCci9FhYwv+2 jdkwD/++GKvvyhxgXHvlWjn6h+qZ/OysZjGMfJsMQTJzn24zzYHLhcZw==
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Thu, May 25, 2023 at 05:22:53PM +0200, Jan Beulich wrote:
> On 25.05.2023 16:54, Roger Pau Monne wrote:
> > When traversing the list of pci devices assigned to a domain cope with
> > some of them not having the vpci struct allocated. It should be
> > possible for the hardware domain to have read-only devices assigned
> > that are not handled by vPCI, such support will be added by further
> > patches.
> >
> > Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
>
> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
Thanks.
> I was wondering whether to put an assertion in (permitting both DomXEN
> and hwdom, i.e. slightly more relaxed than I had it).
I also wondered it, but didn't think it was very helpful, but that was
back when I had the comment about how I envisioned this to work for
domUs.
Let me know if you want me to add it.
Thanks, Roger.
|
