public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Muli Ben-Yehuda <muli-7z/5BgaJwgfQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Ronald Lew <ronald_lew-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Subject: Re: Virtualized hardware and PCI
Date: Sun, 18 Feb 2007 11:54:10 +0200	[thread overview]
Message-ID: <45D82242.4050205@qumranet.com> (raw)
In-Reply-To: <20070218094944.GD2363-WD1JZD8MxeCTrf4lBMg6DdBPR1lH4CV8@public.gmane.org>

Muli Ben-Yehuda wrote:
> On Sun, Feb 18, 2007 at 11:47:07AM +0200, Avi Kivity wrote:
>   
>> Ronald Lew wrote:
>>     
>>> Can Guest OS access abnormal PCI cards such as a fax card or a card designed 
>>> for analog phones (like Digium cards)?  Can the guest OS gain full access to 
>>> the PCI card without going through the virtualization?
>>>       
>> At present this is not supported.  On current hardware it could be made 
>> to work, but only with cards which don't do dma.
>>     
>
> How would you handle device interrupts? take them in the host and then
> inject to the guest through the qemu device emulation?
>
>   

Yes.  Though I now see a problem: masking pci interrupts is not 
standardized, so the host handler cannot shut up the interrupt by 
itself, and of course it cannot rely on the guest doing so.  So without 
some knowledge of the device, all other pci devices that share the same 
interrupt line are at risk.


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      parent reply	other threads:[~2007-02-18  9:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 16:59 Virtualized hardware and PCI Ronald Lew
     [not found] ` <BAY121-F3C2AA87DC35CF1DD93FA7F4950-MsuGFMq8XAE@public.gmane.org>
2007-02-18  9:47   ` Avi Kivity
     [not found]     ` <45D8209B.8040004-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-18  9:49       ` Muli Ben-Yehuda
     [not found]         ` <20070218094944.GD2363-WD1JZD8MxeCTrf4lBMg6DdBPR1lH4CV8@public.gmane.org>
2007-02-18  9:54           ` Avi Kivity [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=45D82242.4050205@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=muli-7z/5BgaJwgfQT0dZR+AlfA@public.gmane.org \
    --cc=ronald_lew-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.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