From: Alex Williamson <alex.williamson@redhat.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: kvm@vger.kernel.org
Subject: Re: problems starting kvm-qemu with 5+ virtual functions
Date: Wed, 11 Jul 2012 14:06:28 -0600 [thread overview]
Message-ID: <1342037188.2229.23.camel@bling.home> (raw)
In-Reply-To: <4FFDDA61.8010509@genband.com>
On Wed, 2012-07-11 at 13:56 -0600, Chris Friesen wrote:
> On 07/11/2012 01:34 PM, Alex Williamson wrote:
> >
> > The limiting factor to increasing memory slots was searching the array.
> > That's since been fixed by caching mmio page table entries.
>
> Thanks for the confirmation of my suspicions.
>
> Do you know roughly when this went in? A commit ID would be great.
Almost exactly a year ago:
ce88decffd17bf9f373cc233c961ad2054965667
next prev parent reply other threads:[~2012-07-11 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 16:52 problems starting kvm-qemu with 5+ virtual functions Chris Friesen
2012-07-11 19:34 ` Alex Williamson
2012-07-11 19:56 ` Chris Friesen
2012-07-11 20:06 ` Alex Williamson [this message]
2012-07-11 21:08 ` Chris Friesen
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=1342037188.2229.23.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=chris.friesen@genband.com \
--cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox