From: Paolo Bonzini <pbonzini@redhat.com>
To: marcel@redhat.com, qemu-devel@nongnu.org
Cc: davidkiarie4@gmail.com, bd.aviv@gmail.com, ehabkost@redhat.com,
peterx@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC 1/2] hw/pci: delay bus_master_enable_region initialization
Date: Mon, 23 May 2016 16:33:23 +0200 [thread overview]
Message-ID: <d3838714-25dd-de8f-a6b0-8970bb08adf2@redhat.com> (raw)
In-Reply-To: <5743120A.703@gmail.com>
On 23/05/2016 16:22, Marcel Apfelbaum wrote:
> On 05/23/2016 05:08 PM, Paolo Bonzini wrote:
>>
>>
>> On 23/05/2016 16:01, Marcel Apfelbaum wrote:
>>> Skip bus_master_enable region creation on PCI devices init
>>> in order to be sure the IOMMU device (if present) would
>>> be created in advance. Add this memory region at machine_done time.
>>>
>>> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
>>> ---
>>> hw/i386/pc.c | 17 +++++++++++++++++
>>> hw/pci/pci.c | 22 ++++++++++++----------
>>> include/hw/pci/pci.h | 2 ++
>>> 3 files changed, 31 insertions(+), 10 deletions(-)
>>
>> Does hotplug still work?
>
> Hotplug does work, but the device can't be bus_master since I am adding
> the bus_master_region only at machine_done...
>
> Thank you for pointing that out, this can be easily solved by checking
> the qdev_hotplug flag and enabling the bus_master region if we passed
> machine creation.
>
> Other than that, does it seems to a you a feasible approach?
Yes, I guess it's okay.
Thanks,
Paolo
next prev parent reply other threads:[~2016-05-23 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 14:01 [Qemu-devel] [PATCH RFC 0/2] enable iommu with -device Marcel Apfelbaum
2016-05-23 14:01 ` [Qemu-devel] [PATCH RFC 1/2] hw/pci: delay bus_master_enable_region initialization Marcel Apfelbaum
2016-05-23 14:08 ` Paolo Bonzini
2016-05-23 14:22 ` Marcel Apfelbaum
2016-05-23 14:33 ` Paolo Bonzini [this message]
2016-05-23 14:01 ` [Qemu-devel] [PATCH RFC 2/2] hw/iommu: enable iommu with -device Marcel Apfelbaum
2016-05-30 13:43 ` [Qemu-devel] [PATCH RFC 0/2] " Peter Xu
2016-05-30 14:14 ` Marcel Apfelbaum
2016-05-31 1:44 ` Peter Xu
2016-06-02 20:30 ` 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=d3838714-25dd-de8f-a6b0-8970bb08adf2@redhat.com \
--to=pbonzini@redhat.com \
--cc=bd.aviv@gmail.com \
--cc=davidkiarie4@gmail.com \
--cc=ehabkost@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@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).