From: David Ahern <dsahern@gmail.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: Avi Kivity <avi@redhat.com>, mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: help? need to enable VT-d for 2.6.27
Date: Tue, 30 Aug 2011 11:55:01 -0600 [thread overview]
Message-ID: <4E5D23F5.3070905@gmail.com> (raw)
In-Reply-To: <4E5D0FF3.6030705@genband.com>
On 08/30/2011 10:29 AM, Chris Friesen wrote:
>
> I'm in a bit of an odd situation. We run an embedded version of linux
> on many different boards with different vendor agreements so it's
> painful to upgrade kernel versions.
>
> I've been asked to provide VT-d support for KVM on our kernel (primarily
> for mapping NIC VFs into the guests), and I'm trying to figure out my
> best option to get a working implementation.
I've had pains with VF passthrough with as late as a Fedora 14 kernel
(2.6.35). Ended up punting and moving to 2.6.39.
>
> Looking at the kvm git tree, kvm-77 seems to be based off 2.6.27. Should
> I look at porting that?
By 2.6.27 do you mean WRL3 or something else?
David
>
> Would I be better off just scanning for anything VT-d related in 2.6.28
> and backporting it?
>
> Are there any better options? Any advice you could provide would be
> appreciated.
>
> Thanks,
> Chris
>
>
next prev parent reply other threads:[~2011-08-30 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 16:29 help? need to enable VT-d for 2.6.27 Chris Friesen
2011-08-30 17:55 ` David Ahern [this message]
2011-08-30 18:11 ` Chris Friesen
2011-08-30 18:31 ` David Ahern
2011-08-30 19:39 ` Chris Friesen
2011-08-30 19:54 ` David Ahern
2011-08-30 19:59 ` Jan Kiszka
2011-08-30 23:03 ` Chris Friesen
2011-08-31 7:30 ` Jan Kiszka
2011-08-31 0:03 ` [BUG] error compiling qemu-kvm-0.15.0 without vnc Chris Friesen
2011-08-31 7:40 ` Jan Kiszka
2011-08-31 8:14 ` Kevin Wolf
2011-08-31 20:11 ` [Qemu-devel] " Justin M. Forbes
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=4E5D23F5.3070905@gmail.com \
--to=dsahern@gmail.com \
--cc=avi@redhat.com \
--cc=chris.friesen@genband.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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