From: benami@il.ibm.com
To: amit.shah@qumranet.com
Cc: weidong.han@intel.com, muli@il.ibm.com, raharper@us.ibm.com,
kvm@vger.kernel.org, Ben-Ami Yassour <benami@il.ibm.com>
Subject: [PATCH] KVM: PCIPT: temporary fix for pio (userspace part)
Date: Tue, 17 Jun 2008 22:25:14 +0300 [thread overview]
Message-ID: <1213730714-10959-2-git-send-email-benami@il.ibm.com> (raw)
In-Reply-To: <1213730714-10959-1-git-send-email-benami@il.ibm.com>
From: Ben-Ami Yassour <benami@il.ibm.com>
PIO for passthrough does not work properly since the permissions are not
set, it is not enough to call iopl at init time.
This temporary patch calls iopl for every pio request.
A better solution would be have a per thread iopl.
An alternative approach would be to use sysfs for pio.
In the mean time, if you want to use the vtd branch, then you probably
need this patch.
Signed-off-by: Ben-Ami Yassour <benami@il.ibm.com>
---
qemu/hw/pci-passthrough.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/qemu/hw/pci-passthrough.c b/qemu/hw/pci-passthrough.c
index 2d916a2..b091a85 100644
--- a/qemu/hw/pci-passthrough.c
+++ b/qemu/hw/pci-passthrough.c
@@ -117,6 +117,7 @@ static void pt_ioport_write##suffix(void *opaque, uint32_t addr, uint32_t value)
r_pio, (int)r_access->e_physbase, \
(unsigned long)r_access->r_virtbase, value); \
} \
+ iopl(3); \
out##suffix(value, r_pio); \
}
--
1.5.5.1
next prev parent reply other threads:[~2008-06-17 19:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 19:05 Patches for vtd pci passthrough benami
2008-06-17 19:05 ` [PATCH] KVM: PCIPT: fix compilation errors benami
2008-06-17 19:05 ` [PATCH] KVM: PCIPT: VT-d: fix guest unmap benami
2008-06-17 19:05 ` [PATCH] KVM: PCIPT: free device structure on vm destroy benami
2008-06-17 19:05 ` [PATCH] KVM: PCIPT: VT-d: fix context mapping benami
2008-06-17 19:25 ` KVM: PCIPT: temporary fix for pio (userspace part) benami
2008-06-17 19:25 ` benami [this message]
2008-06-18 20:30 ` [PATCH] KVM: PCIPT: VT-d: fix context mapping Muli Ben-Yehuda
2008-06-19 8:59 ` Han, Weidong
2008-06-19 12:28 ` Ben-Ami Yassour
2008-06-19 14:18 ` Han, Weidong
2008-06-19 17:44 ` Ben-Ami Yassour1
2008-06-20 6:23 ` Han, Weidong
2008-06-30 15:32 ` Ben-Ami Yassour
2008-07-01 2:22 ` Han, Weidong
2008-06-17 21:29 ` [PATCH] KVM: PCIPT: VT-d: fix guest unmap Anthony Liguori
2008-06-18 12:06 ` Ben-Ami Yassour
2008-06-18 20:48 ` Anthony Liguori
2008-06-18 21:23 ` Muli Ben-Yehuda
2008-06-18 21:41 ` Anthony Liguori
2008-06-20 18:59 ` Avi Kivity
2008-06-20 19:28 ` Anthony Liguori
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=1213730714-10959-2-git-send-email-benami@il.ibm.com \
--to=benami@il.ibm.com \
--cc=amit.shah@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=raharper@us.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox