From: Mohammed Gamal <mgamal@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
pbonzini@redhat.com, Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] amd_iommu: Return error on machines with no PCI
Date: Fri, 15 Sep 2017 11:59:39 +0200 [thread overview]
Message-ID: <1505469579.4717.5.camel@redhat.com> (raw)
In-Reply-To: <20170915020701.GK3617@pxdev.xzpeter.org>
On Fri, 2017-09-15 at 10:07 +0800, Peter Xu wrote:
> On Thu, Sep 14, 2017 at 05:31:38PM -0300, Eduardo Habkost wrote:
> > On Thu, Sep 14, 2017 at 10:24:23PM +0200, Thomas Huth wrote:
> > > On 14.09.2017 22:18, Mohammed Gamal wrote:
> > > > Starting the following command line causes a segfault
> > > > qemu-system-x86_64 -S -machine isapc,accel=kvm -device amd-iommu
> > > >
> > > > This is due to the fact that the machine type 'isapc' doesn't have
> > > > a PCI bus, while amd_iommu doesn't check if the machine has PCI support
> > > > and subsequently does a null-pointer access. AMD IOMMU shouldn't even work
> > > > if the target machine doesn't have PCI.
> > > >
> > > > Add a check for PCI on the given machine type and return an error if PCI
> > > > is not supported.
> > > >
> > > > Signed-off-by: Mohammed Gamal <mgamal@redhat.com>
> > > > ---
> > > > hw/i386/amd_iommu.c | 7 +++++++
> > > > 1 file changed, 7 insertions(+)
> > > >
> > > > diff --git a/hw/i386/amd_iommu.c b/hw/i386/amd_iommu.c
> > > > index 334938a..9a667b7 100644
> > > > --- a/hw/i386/amd_iommu.c
> > > > +++ b/hw/i386/amd_iommu.c
> > > > @@ -1153,6 +1153,13 @@ static void amdvi_realize(DeviceState *dev, Error **err)
> > > > }
> > > >
> > > > bus = pcms->bus;
> > > > +
> > > > + if (!bus) {
> > > > + error_setg(err, "Machine-type '%s' does not support PCI",
> > > > + mc->name);
> > > > + return;
> > > > + }
> > > > +
> > > > s->iotlb = g_hash_table_new_full(amdvi_uint64_hash,
> > > > amdvi_uint64_equal, g_free, g_free);
> > > >
> > > >
> > >
> > > Patch looks fine to me, but I think it would also be sufficient to
> > > change the check at the beginning of the function to test "if (!pcms ||
> > > !pcms->bus)" instead of just "if (!pcms)" ... the error message
> > > "Machine-type 'xxx' not supported by amd-iommu" is also adequate if
> > > there is no PCI bus available on the system.
> >
> > I agree this would be much simpler.
>
> Even, shall we move the pcms && bus check into x86_iommu_realize()
> directly? Then we will only need one single patch for Intel/AMD, and
> it's also a cleanup. Thanks,
Although it's more straight forward to do the checks in amdvi_realize()
and vtd_realize() at the moment, I think moving the checks to
x86_iommu_realize() would be better on the longer term. I will be
sending out a new patch with this change shortly.
Regards,
Mohammed
next prev parent reply other threads:[~2017-09-15 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 20:18 [Qemu-devel] [PATCH] amd_iommu: Return error on machines with no PCI Mohammed Gamal
2017-09-14 20:24 ` Thomas Huth
2017-09-14 20:31 ` Eduardo Habkost
2017-09-15 2:07 ` Peter Xu
2017-09-15 9:59 ` Mohammed Gamal [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-14 19:50 Mohammed Gamal
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=1505469579.4717.5.camel@redhat.com \
--to=mgamal@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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).