qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Bolognani <abologna@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Cc: Marcel Apfelbaum <mapfelba@redhat.com>,
	laine@laine.org, Lukas Doktor <ldoktor@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] Number of usable slots in PCIe Root Port / PCIe Switch Downstream Port
Date: Thu, 24 Aug 2017 10:54:01 +0200	[thread overview]
Message-ID: <1503564841.3438.23.camel@redhat.com> (raw)
In-Reply-To: <ddb6f49e-6617-a659-08bf-cf093f658a8c@redhat.com>

On Wed, 2017-08-23 at 23:16 +0300, Marcel Apfelbaum wrote:
> > Is such a configuration considered valid?
> 
> Definitely no.
> 
> > Or should
> > libvirt and the guest OS / firmware start allowing it?
> 
> I thought libvirt does not allow it anyway and yes, is a bug,
> but considered low priority.

That's correct, libvirt knows those controllers only have
a single slot and will prevent you from adding more than
one device to them. So no change needed there.

IIUC Lukáš is using QEMU directly in (some parts of)
Avocado, so I imagine emitting an error rather than
silently accepting an invalid configuration would save
him some debugging time :) But he knows not to do that
now, so I guess low priority sounds about right.

Thanks for clarifying!

-- 
Andrea Bolognani / Red Hat / Virtualization

      parent reply	other threads:[~2017-08-24  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 16:46 [Qemu-devel] Number of usable slots in PCIe Root Port / PCIe Switch Downstream Port Andrea Bolognani
2017-08-23 20:16 ` Marcel Apfelbaum
2017-08-23 22:19   ` Eduardo Habkost
2017-08-24  8:54   ` Andrea Bolognani [this message]

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=1503564841.3438.23.camel@redhat.com \
    --to=abologna@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=laine@laine.org \
    --cc=ldoktor@redhat.com \
    --cc=mapfelba@redhat.com \
    --cc=marcel@redhat.com \
    --cc=qemu-devel@nongnu.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).