On Sun, Nov 6, 2022 at 1:37 AM Michael S. Tsirkin wrote:
>
> On Fri, Oct 28, 2022 at 02:14:34PM +0800, Jason Wang wrote:
> >
> > -GHashTable *vtd_as_by_busptr; /* VTDBus objects indexed by PCIBus*
> > reference */
> > -VTDBus *vtd_as_by_bus_num[VTD_PCI_BUS_MAX]; /* VTDBus objects indexe
On Fri, Oct 28, 2022 at 02:14:34PM +0800, Jason Wang wrote:
> We introduce VTDBus structure as an intermediate step for searching
> the address space. This works well with SID based matching/lookup. But
> when we want to support SID plus PASID based address space lookup,
> this intermediate steps t
On Sun, Oct 30, 2022 at 6:39 PM Yi Liu wrote:
>
> On 2022/10/28 14:14, Jason Wang wrote:
> > We introduce VTDBus structure as an intermediate step for searching
> > the address space. This works well with SID based matching/lookup. But
> > when we want to support SID plus PASID based address space
On 2022/10/28 14:14, Jason Wang wrote:
We introduce VTDBus structure as an intermediate step for searching
the address space. This works well with SID based matching/lookup. But
when we want to support SID plus PASID based address space lookup,
this intermediate steps turns out to be a burden. So
We introduce VTDBus structure as an intermediate step for searching
the address space. This works well with SID based matching/lookup. But
when we want to support SID plus PASID based address space lookup,
this intermediate steps turns out to be a burden. So the patch simply
drops the VTDBus struct
