From: Alex Williamson <alex.williamson@redhat.com>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: Gleb Natapov <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: RE: VT-d regression issue
Date: Sat, 31 Jul 2010 10:53:29 -0600 [thread overview]
Message-ID: <1280595209.3098.5.camel@x201> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E0AFFF1E6BC@shsmsx502.ccr.corp.intel.com>
On Sat, 2010-07-31 at 16:33 +0800, Hao, Xudong wrote:
> Alex Williamson wrote:
> > On Thu, 2010-07-22 at 16:03 +0300, Gleb Natapov wrote:
> >> On Thu, Jul 22, 2010 at 08:32:31PM +0800, Hao, Xudong wrote:
> >>> Well, this patch works fine for me.
> >>>
> >> Looks like userspace problem then. Userspace relied on something that
> >> was not guarantied by the kernel (access to read only page forwarded
> >> to userspace as MMOI).
> >
> > I just submitted a set of patches that should fix this using the slow
> > mapping path for option ROMs. Thanks,
> >
>
> Alex, I saw your "PCI option ROM fixes" patches in kvm. Does qemu-kvm have corresponding fix for this issue either?
kvm userspace and qemu-kvm are the same thing. Device assignment
currently only lives in the kvm userspace, it it not merged into
upstream qemu. Thanks,
Alex
next prev parent reply other threads:[~2010-07-31 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 7:57 VT-d regression issue Hao, Xudong
2010-07-22 8:21 ` Gleb Natapov
2010-07-22 8:47 ` Hao, Xudong
2010-07-22 8:52 ` Gleb Natapov
2010-07-22 11:09 ` Hao, Xudong
2010-07-22 11:10 ` Gleb Natapov
2010-07-22 11:12 ` Hao, Xudong
2010-07-22 11:11 ` Hao, Xudong
2010-07-22 11:25 ` Gleb Natapov
2010-07-22 12:32 ` Hao, Xudong
2010-07-22 13:03 ` Gleb Natapov
2010-07-30 19:46 ` Alex Williamson
2010-07-31 8:33 ` Hao, Xudong
2010-07-31 16:53 ` Alex Williamson [this message]
2010-08-02 0:52 ` Hao, Xudong
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=1280595209.3098.5.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=xudong.hao@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