mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lv, Zhiyuan" <zhiyuan.lv@intel.com>
To: Roman Shaposhnik <roman@zededa.com>
Cc: Jason Long <hack3rcon@yahoo.com>,
	Mario Marietto <marietto2008@gmail.com>,
	"igvt-g@lists.01.org" <igvt-g@lists.01.org>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Li, Susie" <susie.li@intel.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	"Li, Weinan Z" <weinan.z.li@intel.com>,
	"Downs, Mike" <mike.downs@intel.com>,
	"Xu, Terrence" <terrence.xu@intel.com>
Subject: Re: Various problems for the Xen for XenGT code and guide.
Date: Thu, 3 Sep 2020 10:24:50 +0000	[thread overview]
Message-ID: <7D5BA6A5-3A34-4AF8-9A8C-2010DBB72124@intel.com> (raw)
In-Reply-To: <CAMmSBy8vor1GBqNUSRjj=gNRBwDjzRWFcxuAU0EYkRDgwQ4K+g@mail.gmail.com>

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@zededa.com>
Date: Thursday, September 3, 2020 at 3:56 AM
To: Zhiyuan Lv <zhiyuan.lv@intel.com>
Cc: Jason Long <hack3rcon@yahoo.com>, Mario Marietto <marietto2008@gmail.com>, "igvt-g@lists.01.org" <igvt-g@lists.01.org>, "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Susie Li <susie.li@intel.com>, "Tian, Kevin" <kevin.tian@intel.com>, "Li, Weinan Z" <weinan.z.li@intel.com>, "Downs, Mike" <mike.downs@intel.com>, "Xu, Terrence" <terrence.xu@intel.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@intel.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.


  reply	other threads:[~2020-09-03 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+1FSihpq_i-poiihdF0srE3fGXnncGtCMYqAGmNZu7fjNcY=w@mail.gmail.com>
     [not found] ` <CY4PR11MB15594EC5255084B8AE509068F02E0@CY4PR11MB1559.namprd11.prod.outlook.com>
     [not found]   ` <1093525083.1169948.1598979998646@mail.yahoo.com>
2020-09-02 12:48     ` Lv, Zhiyuan
2020-09-02 19:55       ` Roman Shaposhnik
2020-09-03 10:24         ` Lv, Zhiyuan [this message]
     [not found]       ` <2116380713.1512447.1599053858745@mail.yahoo.com>
2020-09-03 10:33         ` Lv, Zhiyuan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7D5BA6A5-3A34-4AF8-9A8C-2010DBB72124@intel.com \
    --to=zhiyuan.lv@intel.com \
    --cc=hack3rcon@yahoo.com \
    --cc=igvt-g@lists.01.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marietto2008@gmail.com \
    --cc=mike.downs@intel.com \
    --cc=roman@zededa.com \
    --cc=susie.li@intel.com \
    --cc=terrence.xu@intel.com \
    --cc=weinan.z.li@intel.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®