From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: RE: VT-d regression issue Date: Sat, 31 Jul 2010 10:53:29 -0600 Message-ID: <1280595209.3098.5.camel@x201> References: <20100722082122.GE27177@redhat.com> <20100722085209.GF27177@redhat.com> <20100722112503.GB25915@redhat.com> <20100722130338.GA31711@redhat.com> <1280519160.3585.330.camel@x201> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , "kvm@vger.kernel.org" To: "Hao, Xudong" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:5457 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754125Ab0GaQxb (ORCPT ); Sat, 31 Jul 2010 12:53:31 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 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