lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 3 Sep 2020 10:24:50 +0000
From:   "Lv, Zhiyuan" <zhiyuan.lv@...el.com>
To:     Roman Shaposhnik <roman@...eda.com>
CC:     Jason Long <hack3rcon@...oo.com>,
        Mario Marietto <marietto2008@...il.com>,
        "igvt-g@...ts.01.org" <igvt-g@...ts.01.org>,
        "xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
        "xen-devel@...ts.xen.org" <xen-devel@...ts.xen.org>,
        "intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Li, Susie" <susie.li@...el.com>,
        "Tian, Kevin" <kevin.tian@...el.com>,
        "Li, Weinan Z" <weinan.z.li@...el.com>,
        "Downs, Mike" <mike.downs@...el.com>,
        "Xu, Terrence" <terrence.xu@...el.com>
Subject: Re: Various problems for the Xen for XenGT code and guide.

Hi Roman,

Sorry that I am a software guy and can only speak for software. In general there are various approaches to support graphics virtualization. GVT-g as a pure software approach, does not rely on any hardware I/O virtualization features, meanwhile, hypervisors need specific implementations. If the hardware supports standard virtual devices, both Xen and KVM can use them more easily. Thanks!

Regards,
-Zhiyuan

-----Original Message-----
From: Roman Shaposhnik <roman@...eda.com>
Date: Thursday, September 3, 2020 at 3:56 AM
To: Zhiyuan Lv <zhiyuan.lv@...el.com>
Cc: Jason Long <hack3rcon@...oo.com>, Mario Marietto <marietto2008@...il.com>, "igvt-g@...ts.01.org" <igvt-g@...ts.01.org>, "xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>, "xen-devel@...ts.xen.org" <xen-devel@...ts.xen.org>, "intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Susie Li <susie.li@...el.com>, "Tian, Kevin" <kevin.tian@...el.com>, "Li, Weinan Z" <weinan.z.li@...el.com>, "Downs, Mike" <mike.downs@...el.com>, "Xu, Terrence" <terrence.xu@...el.com>
Subject: Re: Various problems for the Xen for XenGT code and guide.

On Wed, Sep 2, 2020 at 5:48 AM Lv, Zhiyuan <zhiyuan.lv@...el.com> wrote:
>
> Hi,
>
> It is mainly due to the business priority change. XenGT project was originally created for data center usages with XEON E3 servers which have integrated processor graphics. After SkyLake E3, there are no new servers capable of running GVT-g, and Intel future graphics for data center will have different approaches for GPU sharing. Another reason is the XenGT upstream difficulty. Different from KVMGT which has been fully merged to upstream, Xen part of GVT-g still has technical opens that are hard to close quickly.

This is extremely useful -- thanks for sharing. Any chance you can
elaborate on the later part "and Intel future graphics for data center
will have different approaches for GPU sharing"?

IOW, is there anything that Intel is cooking up that may help Xen in
that department?

Thanks,
Roman.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ