All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: 'Avi Kivity' <avi@redhat.com>,
	'Subash Kalbarga' <Subashk@ami.com>,
	"'kvm@vger.kernel.org'" <kvm@vger.kernel.org>
Subject: Re: VGA pass-through
Date: Tue, 30 Jun 2009 16:11:14 +0400	[thread overview]
Message-ID: <4A4A00E2.4040905@msgid.tls.msk.ru> (raw)
In-Reply-To: <715D42877B251141A38726ABF5CABF2C0545A1FBA6@pdsmsx503.ccr.corp.intel.com>

Han, Weidong wrote:
> Michael Tokarev wrote:
[]
>> But how about using it as a "secondary" video card?  Like, I can
>> plug another add-on vga card into a free PCI slot and tell X to
>> use that one instead of "default" card.  Can kvm work like this?
> 
> "secondary" means secondary video card in host, and will be "primary" in guest, right? As long as it's primary in guest, I think you still need most of above changes. 

No, I mean "secondary" on guest - no matter if it's secondary or
primary on host.  So that we'll have qemu-emulated VGA as primary
and a hardware-based secondary on *guest*.

How much useful it is - it's another question.  For instance, I've
no idea how windows guest will be able to use such "secondary" vga
card on guest.

/mjt

  reply	other threads:[~2009-06-30 12:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 18:19 VGA pass-through Subash Kalbarga
2009-06-30  6:16 ` Han, Weidong
2009-06-30  6:51   ` Avi Kivity
2009-06-30  7:46     ` Han, Weidong
2009-06-30  8:56       ` Michael Tokarev
2009-06-30  9:37         ` Han, Weidong
2009-06-30 12:11           ` Michael Tokarev [this message]
2009-06-30 12:37             ` Han, Weidong
2009-06-30 13:33               ` Michael Tokarev
2009-06-30 14:01                 ` Subash Kalbarga
2009-08-18 23:27       ` nathan binkert
2009-08-19  3:18         ` Han, Weidong

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=4A4A00E2.4040905@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=Subashk@ami.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=weidong.han@intel.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.