qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aleksandr Bezzubikov <zuban32s@gmail.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
	Marcel Apfelbaum <marcel@redhat.com>
Cc: lersek@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
	seabios@seabios.org
Subject: Re: [Qemu-devel] [PATCH v7 1/4] hw/pci: introduce pcie-pci-bridge device
Date: Wed, 20 Sep 2017 09:52:01 +0000	[thread overview]
Message-ID: <CAKSfGUAS8EfYF179pjQ=svmAL2x-VR_iMTh=cZZjQmz77mO8fQ@mail.gmail.com> (raw)
In-Reply-To: <436365c9-43fc-95be-9bb2-7974f12e84df@redhat.com>

ср, 20 сент. 2017 г. в 10:13, Marcel Apfelbaum <marcel@redhat.com>:

> On 19/09/2017 23:34, Eduardo Habkost wrote:
> > On Fri, Aug 18, 2017 at 02:36:47AM +0300, Aleksandr Bezzubikov wrote:
> >> Introduce a new PCIExpress-to-PCI Bridge device,
> >> which is a hot-pluggable PCI Express device and
> >> supports devices hot-plug with SHPC.
> >>
> >> This device is intended to replace the DMI-to-PCI Bridge.
> >>
> >> Signed-off-by: Aleksandr Bezzubikov <zuban32s@gmail.com>
> >> Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>
> >
> > It's possible to crash QEMU by instantiating this device, with;
> >
> >    $ qemu-system-ppc64 -machine prep -device pcie-pci-bridge
> >    qemu-system-ppc64: qemu/memory.c:1533: memory_region_finalize:
> Assertion `!mr->container' failed.
> >    Aborted
>
> Hi Edurado,
>
> >
> > I didn't investigate the root cause.
> >
>
> Thanks for reporting it!
> Aleksandr, can you have a look? Maybe we should not compile
> the device for ppc arch. (x86 and arm is enough)


I will see what can we do. Is x86 and arm really enough?


>
> Appreciated,
> Marcel
>
> --
Aleksandr Bezzubikov

  reply	other threads:[~2017-09-20 13:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 23:36 [Qemu-devel] [PATCH v7 0/4] Generic PCIE-PCI Bridge Aleksandr Bezzubikov
2017-08-17 23:36 ` [Qemu-devel] [PATCH v7 1/4] hw/pci: introduce pcie-pci-bridge device Aleksandr Bezzubikov
2017-09-19 20:34   ` Eduardo Habkost
2017-09-20  7:13     ` Marcel Apfelbaum
2017-09-20  9:52       ` Aleksandr Bezzubikov [this message]
2017-09-20 13:57         ` Eduardo Habkost
2017-09-20 14:02           ` Marcel Apfelbaum
2017-09-20 20:04             ` Aleksandr Bezzubikov
2017-09-20 14:00         ` Marcel Apfelbaum
2017-08-17 23:36 ` [Qemu-devel] [PATCH v7 2/4] hw/pci: introduce bridge-only vendor-specific capability to provide some hints to firmware Aleksandr Bezzubikov
2017-08-17 23:36 ` [Qemu-devel] [PATCH v7 3/4] hw/pci: add QEMU-specific PCI capability to the Generic PCI Express Root Port Aleksandr Bezzubikov
2017-08-17 23:36 ` [Qemu-devel] [PATCH v7 4/4] docs: update documentation considering PCIE-PCI bridge Aleksandr Bezzubikov
2017-08-22 11:43 ` [Qemu-devel] [PATCH v7 0/4] Generic PCIE-PCI Bridge Marcel Apfelbaum
2017-08-23  2:46   ` Michael S. Tsirkin
2017-09-06  1:01     ` Aleksandr Bezzubikov

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='CAKSfGUAS8EfYF179pjQ=svmAL2x-VR_iMTh=cZZjQmz77mO8fQ@mail.gmail.com' \
    --to=zuban32s@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).