From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: Byron Stanoszek <bstanoszek@comtime.com>,
Amit Shah <amit.shah@qumranet.com>,
kvm@vger.kernel.org
Subject: Re: VT-d support for device assignment
Date: Fri, 22 Aug 2008 21:23:29 +0300 [thread overview]
Message-ID: <20080822182329.GG6885@il.ibm.com> (raw)
In-Reply-To: <48AF0190.3010103@qumranet.com>
On Fri, Aug 22, 2008 at 09:12:32PM +0300, Avi Kivity wrote:
> Muli Ben-Yehuda wrote:
> > With PCI passthrough It is possible in theory to log mmio's and pio's
> > executed by the guest, as well as interrupts delivered to the guest,
> > although it will have a performance impact. It is not possible to log
> > DMAs in a simple manner, but you could hook up a PCI analyzer to get
> > the missing bits.
> >
>
> Well, with a pci analyzer you can log anything going in and out of
> the device; you don't need a virtual machine monitor.
Yep, that's true. I was thinking along the lines of doing the bulk of
reverse engineering without a PCI analyzer (if you understand the
device well enough, looking at the DMA data may not be all that
important) and then using a PCI analyzer just for any remaining bits.
By the way, with effort we should be able to capture some DMAs too,
either by taking "before" and "after" snapshots of VM memory (for DMA
write to memory) and/or by triggering DMA faults (by not mapping the
VM's memory in an isolation-capable IOMMU and enabling the IOMMU).
Cheers,
Muli
--
Workshop on I/O Virtualization (WIOV '08)
Co-located with OSDI '08, Dec 2008, San Diego, CA
http://www.usenix.org/wiov08
next prev parent reply other threads:[~2008-08-22 18:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 7:10 VT-d support for device assignment Amit Shah
2008-08-22 7:10 ` [PATCH] VT-d: changes to support KVM Amit Shah
2008-08-22 7:10 ` [PATCH] KVM: Device Assignment with VT-d Amit Shah
2008-08-23 16:21 ` [PATCH] VT-d: changes to support KVM Jesse Barnes
2008-08-22 13:54 ` VT-d support for device assignment Byron Stanoszek
2008-08-22 15:32 ` Amit Shah
2008-08-22 18:29 ` Muli Ben-Yehuda
2008-08-22 18:37 ` Avi Kivity
2008-08-22 19:09 ` Muli Ben-Yehuda
2008-08-22 16:08 ` Muli Ben-Yehuda
2008-08-22 18:12 ` Avi Kivity
2008-08-22 18:23 ` Muli Ben-Yehuda [this message]
2008-08-22 18:21 ` Avi Kivity
2008-08-22 18:28 ` Muli Ben-Yehuda
2008-08-23 9:12 ` Amit Shah
2008-08-23 9:33 ` Avi Kivity
2008-08-23 9:49 ` Amit Shah
2008-08-24 10:01 ` Avi Kivity
2008-08-23 9:50 ` Muli Ben-Yehuda
2008-08-23 9:55 ` Muli Ben-Yehuda
2008-08-24 10:02 ` Avi Kivity
2008-08-23 9:57 ` Muli Ben-Yehuda
2008-08-23 10:25 ` Amit Shah
2008-08-23 10:40 ` Muli Ben-Yehuda
2008-08-23 11:11 ` Amit Shah
2008-08-23 12:11 ` Muli Ben-Yehuda
2008-08-23 14:01 ` Amit Shah
2008-09-01 13:08 ` Joerg Roedel
-- strict thread matches above, loose matches on Subject: below --
2008-09-09 15:37 Amit Shah
2008-09-14 0:46 ` Avi Kivity
2008-09-23 18:57 ` Jesse Barnes
2008-09-09 14:44 Amit Shah
2008-09-09 13:50 Han, Weidong
2008-08-26 8:55 Amit Shah
2008-08-26 9:10 ` Avi Kivity
2008-08-26 14:11 ` Amit Shah
2008-08-26 14:38 ` Avi Kivity
2008-08-21 11:10 Ben-Ami Yassour
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=20080822182329.GG6885@il.ibm.com \
--to=muli@il.ibm.com \
--cc=amit.shah@qumranet.com \
--cc=avi@qumranet.com \
--cc=bstanoszek@comtime.com \
--cc=kvm@vger.kernel.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