All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Sergey Tovpeko <tsv.devel@gmail.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: xl and GFX passthrough
Date: Wed, 26 Jan 2011 10:01:25 -0500	[thread overview]
Message-ID: <4D403745.3060008@tycho.nsa.gov> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D53019434A445@orsmsx505.amr.corp.intel.com>

On 01/25/2011 09:49 PM, Kay, Allen M wrote:
> Sergey,
> 
> Did you get gfx_passthru to work with xl?  I found the latest source still does not seems to pass gfx_passthru to qemu correctly.
> 
> By the way, how to output debug messages to xl*.log file?  I tried LOG() and fprintf(stderr...) neither worked for me.
> 
> Allen
> 
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Sergey Tovpeko
> Sent: Thursday, January 13, 2011 3:18 AM
> To: Ian Campbell; Daniel De Graaf
> Cc: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] xl and GFX passthrough
> 
> 
>>
>> I just noticed that this appears to have been fixed by Daniel De Graf
>> just a few days ago, see 22711:4f6fee3a456e, which may only be in the
>> staging tree at http://xenbits.xen.org/staging/xen-unstable.hg since we
>> are waiting for a test pass.
>>
>>   
> 
> Ian, Daniel
>  
>   my patch is almost like Daniel's one.  Thank you for pointing to it.
> 
> And there's one absent thing in Daniel's commit (4f6fee3a456e). To 
> complete the gfx passthrough issue for xl we should pass this option to 
> qemu-dm, like this :
> 
> +        if (info->gfx_passthru) {
> +            flexarray_set(dm_args, num++, "-gfx_passthru");
> +            flexarray_set(dm_args, num++, libxl__sprintf(gc, "%d", 
> info->gfx_passthru));
> +        }
> 
> I suppose, without it 'qemu-dm' won't  know about gfx_passthru mode and 
> won't load passthru'ed vga bios.
> 
> Daniel might plan to add this code or added it already?
> 

Actually, I hadn't noticed that gfx_passthru takes an (apparently optional)
numeric parameter. This change is more correct than the one I posted,
although it also needs gfx_passthru to be changed from bool to int in the
IDL (assuming that -gfx_passthru 2 is still useful, I hadn't heard of it
until recently).

Kay: sounds like you have this fixed in your tree, I'll let you or Ian
fix it.

-- 
Daniel De Graaf
National Security Agency

      parent reply	other threads:[~2011-01-26 15:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13  9:12 xl and GFX passthrough Sergey Tovpeko
2011-01-13  9:26 ` Ian Campbell
2011-01-13 10:05   ` Sergey Tovpeko
2011-01-13 10:24     ` Ian Campbell
2011-01-13 11:17       ` Sergey Tovpeko
2011-01-13 11:28         ` Ian Campbell
2011-01-13 11:33           ` Ian Jackson
2011-01-17 17:48             ` Ian Jackson
2011-01-26  2:49         ` Kay, Allen M
2011-01-26 10:24           ` Stefano Stabellini
2011-01-26 15:01           ` Daniel De Graaf [this message]

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=4D403745.3060008@tycho.nsa.gov \
    --to=dgdegra@tycho.nsa.gov \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=allen.m.kay@intel.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tsv.devel@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.