From: Avi Kivity <avi@redhat.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: when will kvm merge update from upstream linux?
Date: Mon, 20 Aug 2012 13:45:04 +0300 [thread overview]
Message-ID: <50321530.1080503@redhat.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A101588F8@SHSMSX101.ccr.corp.intel.com>
On 08/20/2012 01:32 PM, Ren, Yongjie wrote:
> Hi Avi,
> With latest kvm.git tree, igb VF can't be enabled.
> But it can work fine with upstream linux.git tree.
> When will kvm merge the latest update in upstream linux?
> The following commit in upstream linux.git should be the fix.
It is in auto-next, I recommend you test that branch.
>
> commit 7f46f9c13041c8fde331142791f3994a8fdbec6f
> Merge: 6666cab 31fe943
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Wed Aug 8 20:01:45 2012 +0300
>
> Merge tag 'iommu-fixes-v3.6-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
>
> Pull IOMMU fixes from Joerg Roedel:
> "These patches fix a couple of issues. First of all a few problems
> with ACS on x86 introduced in the last merge window, where ACS did not
> work on AMD and a NULL pointer dereference when there ran against
> SR-IOV devices.
>
> The patches fallen out of coccinelle checks fix a possible invalid
> memory reference and a possible memory leak. The other patches mostly
> fix build errors and warnings and a wrong return value."
>
>
> Best Regards,
> Yongjie (Jay)
>
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-08-20 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 10:32 when will kvm merge update from upstream linux? Ren, Yongjie
2012-08-20 10:45 ` Avi Kivity [this message]
2012-08-20 10:57 ` Ren, Yongjie
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=50321530.1080503@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=yongjie.ren@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