qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/pci: do not update the PCI mappings while Decode (I/O or memory) bit is not set in the Command register
Date: Thu, 14 Jan 2016 17:23:27 +0200	[thread overview]
Message-ID: <5697BD6F.7030501@redhat.com> (raw)
In-Reply-To: <20160114164309-mutt-send-email-mst@redhat.com>

On 01/14/2016 04:49 PM, Michael S. Tsirkin wrote:
> On Thu, Jan 14, 2016 at 03:30:41PM +0100, Laszlo Ersek wrote:
>>> 2. The same as with pxb, disable Integrated End points for pxb-pcie.
>>
>> My vote, without a doubt.
>
> Yea, me too.
>
>
> On a related note: I wonder whether enough resources will be allocated
> to the bridge to actually make it possible to add devices by hotplug
> later.
>

It works the same as with PXB, but now instead of having one internal PCI-bridge,
we will have several switches/root ports. Each of them will get the minimum MEM required by
PCI bridges, however the IO will be allocated only if at least one legacy device
will be present at boot time. (this is at least what SeaBIOS does, I am going to check OVMF actions)

Also related, checking that PCIe native hotplug works for devices behind
pxb-pcie bridges is my next step after I fix the current issue.

Thanks,
Marcel

>
>>>
>>> I am going to look at 1., maybe I is doable in a clean way.
>>
>> My vote: don't. :)
>>
>> Thanks
>> Laszlo
>>
>>> Thanks,
>>> Marcel
>>>
>>>
>>> [...]

  reply	other threads:[~2016-01-14 15:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 12:24 [Qemu-devel] [PATCH] hw/pci: do not update the PCI mappings while Decode (I/O or memory) bit is not set in the Command register Marcel Apfelbaum
2016-01-11 14:07 ` Igor Mammedov
2016-01-11 15:10   ` Marcel Apfelbaum
2016-01-11 16:11 ` Laszlo Ersek
2016-01-11 16:34   ` Marcel Apfelbaum
2016-01-11 17:15     ` Laszlo Ersek
2016-01-11 18:01       ` Marcel Apfelbaum
2016-01-11 18:44         ` Laszlo Ersek
2016-01-11 18:57           ` Marcel Apfelbaum
2016-01-14 12:24             ` Marcel Apfelbaum
2016-01-14 14:30               ` Laszlo Ersek
2016-01-14 14:49                 ` Michael S. Tsirkin
2016-01-14 15:23                   ` Marcel Apfelbaum [this message]
2016-01-14 15:37                     ` Michael S. Tsirkin
2016-01-14 17:20                       ` Marcel Apfelbaum
2016-01-14 17:28                         ` Michael S. Tsirkin
2016-01-14 18:25                           ` Marcel Apfelbaum
2016-01-14 15:14                 ` Marcel Apfelbaum

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=5697BD6F.7030501@redhat.com \
    --to=marcel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mst@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).