Re: [XenGT][IGVT-g] DomU pgt_device structure initialization

[Oleksii Kurochko <oleksii.kurochko@globallogic.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1313 bytes --]

Hello.

Looks you didn’t set IRQ_INFO_GT for BCS event. Is it a typo?
>
Yeap, it was typo.

I will look at debug inforamtion that U told.

Thanks.

On Thu, Jan 14, 2016 at 7:44 AM, Tian, Kevin <kevin.tian@intel.com> wrote:

> if (IS_VLV(pdev)) {
>
>  SET_BIT_INFO(hstate, 2, RCS_MMIO_SYNC_FLUSH, IRQ_INFO_GT);
>
>  SET_BIT_INFO(hstate, 14, VCS_MMIO_SYNC_FLUSH, IRQ_INFO_GT);
>
>  SET_BIT_INFO(hstate, 24, BCS_MMIO_SYNC_FLUSH);
> }
>
>
>
> Looks you didn’t set IRQ_INFO_GT for BCS event. Is it a typo?
>
>
>
> Generally you can look at /sys/kernel/debug/vgt/irqinfo to see virtual
> event injection status, which may give some hint.
>
>
>
> In your log there is hangcheck triggered in Dom0:
>
> [   51.521359] vGT info:(vgt_handle_dom0_device_reset:940) DOM0 hangcheck
> timer request reset device.
>
> It means GPU is already hung.
>
>
>
> I don’t have an immediate idea now since this is only an experimental code
> and not sure how much your hardware is different from its assume
> configuration.
>
>
>
> A simpler case might be to just run some 3D workloads within Dom0 to see
> whether it works well, and then try launch another guest later.
>
>
>
> Thanks
>
> Kevin
>



-- 
Oleksii Kurochko | Embedded Dev
GlobalLogic
www.globallogic.com

[-- Attachment #1.2: Type: text/html, Size: 5214 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel