From: Avi Kivity <avi@redhat.com>
To: Vikram Ambrose <vambrose@gmx.com>
Cc: kvm@vger.kernel.org
Subject: Re: pci-passthrough logging
Date: Sun, 21 Feb 2010 11:47:50 +0200 [thread overview]
Message-ID: <4B810146.3010601@redhat.com> (raw)
In-Reply-To: <4B7F25B9.3010000@gmx.com>
On 02/20/2010 01:58 AM, Vikram Ambrose wrote:
> Hello,
>
> I'm new to kvm and I'm trying to log pci config and mmio read/writes
> for a particular pci (pci-e to be precise) device that I've
> passthrough to qemu-kvm (dma=none).
>
> I put a printk into kvm_iodevice_read/write() in
> linux/virt/kvm/iodev.h but the log seems to get corrupted when the
> action picks up.
>
> I looked at qemu-kvm/hw/pci_host.c and found
> pci_host_data_write/read_mmio[]. But I don't know where those are
> implemented, nor exactly what they do for that matter.
>
> I appologise for the n00b nature of my problem, but there isnt any
> documentation on the pci-passthrough architecture in
> linux/Documentation/kvm or in qemu-kvm.
>
> Does anyone know where/how to log pci-passthrough accesses?
For config-space accesses, hook assigned_dev_pci_{read,write}_config().
For mmio, hook slow_bar_{read,write}*(), and hack
assigned_dev_register_regions() to select the slow path (otherwise kvm
will let the guest write directly to the device). For pio, hook
assigned_dev_ioport_{read,write)*().
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-02-21 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 23:58 pci-passthrough logging Vikram Ambrose
2010-02-21 9:47 ` 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=4B810146.3010601@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=vambrose@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox