From: Alexander Graf <agraf@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>,
aik@ozlabs.ru, mdroth@us.ibm.com
Cc: pbonzini@redhat.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pseries: Limit PCI host bridge "index" value
Date: Thu, 29 Jan 2015 14:12:41 +0100 [thread overview]
Message-ID: <54CA31C9.2080406@suse.de> (raw)
In-Reply-To: <1421202819-19860-1-git-send-email-david@gibson.dropbear.id.au>
On 14.01.15 03:33, David Gibson wrote:
> pseries guests can have large numbers of PCI host bridges. To avoid the
> user having to specify a number of different configuration values for every
> one, the device supports an "index" property which is a shorthand setting
> the various window and configuration addresses from a predefined sensible
> set.
>
> There are some problems with the details at present:
> * The "index" propery is signed, but negative values will create PCI
> windows below where we expect, potentially colliding with other devices
> * No limit is imposed on the "index" property and large values can
> translate to extremely large window addresses. With PCI passthrough in
> particular this can mean we exceed various mapping and physical address
> limits causing the guest host bridge to not work in strange ways.
>
> This patch addresses this, by making "index" unsigned, and imposing a
> limit. Currently the limit allows indices from 0..255 which is probably
> enough host bridges for the time being. It's fairly easy to extend if
> we discover we need more.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Thanks, applied to ppc-next.
Alex
prev parent reply other threads:[~2015-01-29 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 2:33 [Qemu-devel] [PATCH] pseries: Limit PCI host bridge "index" value David Gibson
2015-01-14 12:10 ` Paolo Bonzini
2015-01-14 17:23 ` Michael Roth
2015-01-15 1:38 ` David Gibson
2015-01-29 0:37 ` David Gibson
2015-01-29 13:12 ` Alexander Graf [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=54CA31C9.2080406@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.