xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. Greg Wettstein" <greg@wind.enjellic.com>
To: Oleksii Kurochko <oleksii.kurochko@globallogic.com>,
	"Tian, Kevin" <kevin.tian@intel.com>
Cc: "igvt-g@lists.01.org" <igvt-g@ml01.01.org>,
	"Li, Susie" <susie.li@intel.com>,
	"Dong, Eddie" <eddie.dong@intel.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [XenGT][IGVT-g] DomU pgt_device structure initialization
Date: Thu, 21 Jan 2016 12:56:03 -0600	[thread overview]
Message-ID: <201601211856.u0LIu3JU018177@wind.enjellic.com> (raw)
In-Reply-To: Oleksii Kurochko <oleksii.kurochko@globallogic.com> "Re: [Xen-devel] [XenGT][IGVT-g] DomU pgt_device structure initialization" (Jan 5, 10:04am)

On Jan 5, 10:04am, Oleksii Kurochko wrote:
} Subject: Re: [Xen-devel] [XenGT][IGVT-g] DomU pgt_device structure initial

> Hey.

Hi Oleksii, I hope this note finds your day going well.

> Strange for me was that I got vmid=0 and gen_type=0, so I decided go
> to i915_gem_vgtbuffer_ioctl and write next at the start: if
> (!xen_initial_domain()) { return -EPERM; } Also same code is in 3.17
> kernel from XenGT-kernel repo.
>
> it seems that there is no more this error now( from vgt_fb_decoder ), BUT
> there is often freeze or very laggy UI in guest.
> 
> What it can be?

It wasn't in this e-mail but I went through the console logs which
were in one of your postings on the IGVT-g list.  I believe you have
your hypervisor configured for synchronous serial console output
(sync_console command-line parameter) and you are directing your dom0
kernel console logging through the Xen provided serial interface.

Setting this option is documented to cause significant latencies.  In
fact there is a warning about this in the Xen console logs when the
hypervisor boots.  Here is the code snippet from
 xen/drivers/char/console.c:console_endboot() which produces the
message:

if ( opt_sync_console )
{
	printk("**********************************************\n");
        printk("******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS\n");
        printk("******* This option is intended to aid debugging "
               "of Xen by ensuring\n");
        printk("******* that all output is synchronously delivered "
               "on the serial line.\n");
        printk("******* However it can introduce SIGNIFICANT latencies "
               "and affect\n");
        printk("******* timekeeping. It is NOT recommended for "
               "production use!\n");
        printk("**********************************************\n");


It appears as if you were generating significant amounts of kernel log
output which may be at the root of the unacceptable latencies.  I
would start by turning off that option and see if your guest
performance improves.

> With best regards,
>  Oleksii

Good luck with your work.

Greg

}-- End of excerpt from Oleksii Kurochko

As always,
Dr. G.W. Wettstein, Ph.D.   Enjellic Systems Development, LLC.
4206 N. 19th Ave.           Specializing in information infra-structure
Fargo, ND  58102            development.
PH: 701-281-1686
FAX: 701-281-3949           EMAIL: greg@enjellic.com
------------------------------------------------------------------------------
"Sweeny's Law: The length of a progress report is inversely proportional
 to the amount of progress."

-- 

             reply	other threads:[~2016-01-21 18:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 18:56 Dr. Greg Wettstein [this message]
2016-01-22  9:34 ` [XenGT][IGVT-g] DomU pgt_device structure initialization Oleksii Kurochko
  -- strict thread matches above, loose matches on Subject: below --
2016-01-03 19:48 Oleksii Kurochko
2016-01-05  6:07 ` Tian, Kevin
2016-01-05  8:04   ` Oleksii Kurochko
2016-01-11  5:07     ` Tian, Kevin
2016-01-11  5:44       ` Oleksii Kurochko
2016-01-11  5:50         ` Tian, Kevin
2016-01-13 16:45           ` Oleksii Kurochko
2016-01-13 16:58             ` Oleksii Kurochko
2016-01-14  5:44               ` Tian, Kevin
2016-01-18  7:28                 ` Oleksii Kurochko

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=201601211856.u0LIu3JU018177@wind.enjellic.com \
    --to=greg@wind.enjellic.com \
    --cc=eddie.dong@intel.com \
    --cc=greg@enjellic.com \
    --cc=igvt-g@ml01.01.org \
    --cc=kevin.tian@intel.com \
    --cc=kraxel@redhat.com \
    --cc=oleksii.kurochko@globallogic.com \
    --cc=susie.li@intel.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).