qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: Marcel Apfelbaum <marcel@redhat.com>,
	"Kinsella, Ray" <ray.kinsella@intel.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	seabios@seabios.org, Gerd Hoffmann <kraxel@redhat.com>,
	Michael Tsirkin <mst@redhat.com>
Subject: Re: [Qemu-devel] >256 Virtio-net-pci hotplug Devices
Date: Sun, 23 Jul 2017 16:04:40 -0400	[thread overview]
Message-ID: <20170723200440.GA3718@morn.lan> (raw)
In-Reply-To: <97068eca-2788-8396-0f8d-1990c651bdfc@redhat.com>

On Sun, Jul 23, 2017 at 07:28:01PM +0300, Marcel Apfelbaum wrote:
> On 22/07/2017 2:57, Kinsella, Ray wrote:
> > When scaling up to 512 Virtio-net devices SeaBIOS appears to really slow
> > down when configuring PCI Config space - haven't manage to get this to
> > work yet.

If there is a slowdown in SeaBIOS, it would help to produce a log with
timing information - see:
https://www.seabios.org/Debugging#Timing_debug_messages

It may also help to increase the debug level in SeaBIOS to get more
fine grained timing reports.

-Kevin

  reply	other threads:[~2017-07-23 20:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 21:50 [Qemu-devel] >256 Virtio-net-pci hotplug Devices Kinsella, Ray
2017-07-18 13:49 ` Marcel Apfelbaum
2017-07-20  0:44   ` Kinsella, Ray
2017-07-21  8:33     ` Marcel Apfelbaum
2017-07-21 23:57       ` Kinsella, Ray
2017-07-23 16:28         ` Marcel Apfelbaum
2017-07-23 20:04           ` Kevin O'Connor [this message]
2017-07-24  4:53             ` Kinsella, Ray
2017-07-24  7:14               ` Marcel Apfelbaum
2017-07-25 18:00                 ` Kinsella, Ray
2017-08-02 12:43                   ` Marcel Apfelbaum
2017-08-07 19:00                     ` Kinsella, Ray
2017-08-09 10:53                       ` Marcel Apfelbaum
2017-08-09 16:36                         ` Kinsella, Ray

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=20170723200440.GA3718@morn.lan \
    --to=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ray.kinsella@intel.com \
    --cc=seabios@seabios.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;
as well as URLs for NNTP newsgroup(s).