On 11/10/16 at 12:52pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> thanks for working on this, really appreciated!
>
> On Thu, Oct 20, 2016 at 07:37:11PM +0800, Baoquan He wrote:
> > This is v6 post.
> >
> > The principle of the fix is similar to intel iommu. Just defer the
> > assignment
> > of de
Hi Baoquan,
thanks for working on this, really appreciated!
On Thu, Oct 20, 2016 at 07:37:11PM +0800, Baoquan He wrote:
> This is v6 post.
>
> The principle of the fix is similar to intel iommu. Just defer the assignment
> of device to domain to device driver init. But there's difference than
>
On 11/04/16 at 01:14pm, Baoquan He wrote:
> Hi Joerg,
>
> Ping!
>
> About the v6 post, do you have any suggestions?
>
> Because of GCR3 special handling in patch 9/9, I spent several days to
> study the knowledge and change code. Then when I tried to post, the
> virtual interrupt remapping featu
Hi Joerg,
Ping!
About the v6 post, do you have any suggestions?
Because of GCR3 special handling in patch 9/9, I spent several days to
study the knowledge and change code. Then when I tried to post, the
virtual interrupt remapping feature caused kernel hang with this pachset
applied. So it took
This is v6 post.
The principle of the fix is similar to intel iommu. Just defer the assignment
of device to domain to device driver init. But there's difference than
intel iommu. AMD iommu create protection domain and assign device to
domain in iommu driver init stage. So in this patchset I just
5 matches
Mail list logo