From: Peter Xu <peterx@redhat.com>
To: Mohammed Gamal <mgamal@redhat.com>
Cc: qemu-devel@nongnu.org, ehabkost@redhat.com, mst@redhat.com,
thuth@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/2] x86_iommu: Fix segfault when starting on non-PCI machines
Date: Mon, 18 Sep 2017 17:29:08 +0800 [thread overview]
Message-ID: <20170918092908.GF3617@pxdev.xzpeter.org> (raw)
In-Reply-To: <1505487877-22799-1-git-send-email-mgamal@redhat.com>
On Fri, Sep 15, 2017 at 05:04:35PM +0200, Mohammed Gamal wrote:
> Starting qemu with
> qemu-system-x86_64 -S -M isapc -device {amd|intel}-iommu
> leads to a segfault. The code assume PCI bus is present and
> tries to access the bus structure without checking.
>
> The patch series moves the error checks from vtd_realize()
> and amdvi_realize() to the generic x86_iommu_realize() and
> adds a check for PCI bus presence.
>
> v1 --> v2:
> * Change error message with capitalized acronym
>
> Mohammed Gamal (2):
> x86_iommu: Move machine check to x86_iommu_realize()
> x86_iommu: check if machine has PCI bus
I'm fine with even keeping object_dynamic_cast() there in patch 1, but
I agree with Eduardo's questioning.
For either case:
Reviewed-by: Peter Xu <peterx@redhat.com>
>
> hw/i386/amd_iommu.c | 10 +---------
> hw/i386/intel_iommu.c | 10 +---------
> hw/i386/x86-iommu.c | 13 +++++++++++++
> 3 files changed, 15 insertions(+), 18 deletions(-)
>
> --
> 1.8.3.1
>
--
Peter Xu
prev parent reply other threads:[~2017-09-18 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 15:04 [Qemu-devel] [PATCH v2 0/2] x86_iommu: Fix segfault when starting on non-PCI machines Mohammed Gamal
2017-09-15 15:04 ` [Qemu-devel] [PATCH v2 1/2] x86_iommu: Move machine check to x86_iommu_realize() Mohammed Gamal
2017-09-15 22:27 ` Eduardo Habkost
2017-09-15 15:04 ` [Qemu-devel] [PATCH v2 2/2] x86_iommu: check if machine has PCI bus Mohammed Gamal
2017-09-18 9:29 ` Peter Xu [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=20170918092908.GF3617@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mgamal@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).