All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kaushik Barde" <Kaushik_Barde@Phoenix.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: RE: Selective Passthrough Virtualization
Date: Mon, 22 Jan 2007 11:07:50 -0800	[thread overview]
Message-ID: <0EF82802ABAA22479BC1CE8E2F60E8C301609A57@scl-exch2k3.phoenix.com> (raw)
In-Reply-To: C1DA2AF4.7963%Keir.Fraser@cl.cam.ac.uk

Thanks Keir,

I understand. 

So, I assume with extra-chipset support you meant something like :

- SVIF ( Self-Virtualized Interfaces) based Sound-cards with its
(addition to sound functions) own memory addressing scheme and audio
processor facilitating virtualized interfaces.

Looks like we may have to Resort to Xen//Dom0 handling of audio 
	- How good is it?

Thanks.

-Kaushik

-----Original Message-----
From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] 
Sent: Monday, January 22, 2007 12:49 AM
To: Kaushik Barde; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Selective Passthrough Virtualization 

On 22/1/07 6:13 am, "Kaushik Barde" <Kaushik_Barde@Phoenix.com> wrote:

> I was trying to get Xen-FC5 DOM0 to allow Windows-XP to have 100%
control of
> the sound device on the VT enabled HW platform.  After poking at this
for a
> bit we ended up in a place where we though the current Xen didn't
support this
> without having custom drivers that understood it was being
virtualized.   Have
> you found a way around this?

It's unlikely to be possible because the device's DMA engine will expect
to
be programmed with physical memory addresses, but the Windows guest only
sees virtualised physical addresses so it will program incorrect values
and
DMA to random places. Extra chipset support (which isn't yet available)
is
required to support real device drivers in fully virtualised guests.

 -- Keir

      parent reply	other threads:[~2007-01-22 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22  6:13 Selective Passthrough Virtualization Kaushik Barde
2007-01-22  8:48 ` Keir Fraser
2007-01-22 10:40   ` Petersson, Mats
2007-01-22 19:07   ` Kaushik Barde [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=0EF82802ABAA22479BC1CE8E2F60E8C301609A57@scl-exch2k3.phoenix.com \
    --to=kaushik_barde@phoenix.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.