From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, "Roedel, Joerg" <Joerg.Roedel@amd.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: vfio: missing patch in linux 3.6
Date: Thu, 04 Oct 2012 17:57:22 +0200 [thread overview]
Message-ID: <506DB1E2.9060006@01019freenet.de> (raw)
In-Reply-To: <1349364399.2759.42.camel@ul30vt.home>
Alex Williamson wrote:
> On Thu, 2012-10-04 at 17:13 +0200, Andreas Hartmann wrote:
>> Hello Alex,
>>
>> I just tested vfio as part of linux 3.6 and detected, that it
>> doesn't work because of the following missing patch:
>>
>> http://news.gmane.org/find-root.php?group=gmane.linux.kernel.pci&article=16422
>>
>>
>>
Could you please get it applied for the next stable release?
>
> Hi Andreas,
>
> This patch needs to go through Bjorn's PCI tree, but as noted in
> the comments I have some outstanding questions that need to be
> answered, probably by Joerg. Thanks,
Sorry Alex,
I missed your additional questions because this patch just works
pretty fine here with kernel 3.4.x.
But you're right, your questions should be resolved before freeing it
to the wild.
@Joerg:
Please, liberate me from compiling and patching each kernel myself to
get it working and give all the other users out there a chance to use
this pretty code and the IOMMU support of AMD's hardware :-) by
answering Alex' questions.
Thanks,
kind regards,
Andreas
next prev parent reply other threads:[~2012-10-04 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 15:13 vfio: missing patch in linux 3.6 Andreas Hartmann
2012-10-04 15:26 ` Alex Williamson
2012-10-04 15:57 ` Andreas Hartmann [this message]
2012-10-04 16:14 ` Roedel, Joerg
2012-10-04 16:28 ` Alex Williamson
2012-10-05 13:08 ` Roedel, Joerg
2012-10-14 15:07 ` Andreas Hartmann
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=506DB1E2.9060006@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=Joerg.Roedel@amd.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.