From: Alex Williamson <alex.williamson@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Singh, Brijesh" <brijesh.singh@amd.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Peter Xu <zhexu@redhat.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>
Subject: Re: [Qemu-devel] [RFC PATCH] pci: Use PCI aliases when determining device IOMMU address space
Date: Thu, 25 Jul 2019 08:00:23 -0600 [thread overview]
Message-ID: <20190725080023.24de0d82@x1.home> (raw)
In-Reply-To: <20190725064244-mutt-send-email-mst@kernel.org>
On Thu, 25 Jul 2019 06:43:04 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Thu, Jul 25, 2019 at 02:37:33PM +0800, Peter Xu wrote:
> > After re-read Michael's reply, I feel like what Michael suggested is
> > that we can simply ignore the bus-number-change case by the guest OS
> > for now, but I might be wrong.
> That's what I suggested, yes.
"by the guest OS", yes, that's the part that's beyond the scope of this
effort. If we deem it necessary to support IVHD DMA alias though, it's
the guest firmware that determines the initial bus numbers, which is
part of the DeviceID used to defined IVHD entries and we would not be
able to ignore that initial programming. Everything related to the
guest OS renumber PCI buses is out of scope, the guest firmware
programming initial bus numbers is not. Thanks,
Alex
next prev parent reply other threads:[~2019-07-25 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <155364082689.15803.7062874513041742278.stgit@gimli.home>
[not found] ` <20190329104904.450fefef@x1.home>
2019-04-01 13:41 ` [Qemu-devel] [RFC PATCH] pci: Use PCI aliases when determining device IOMMU address space Singh, Brijesh
2019-07-23 17:26 ` Alex Williamson
2019-07-23 18:45 ` Michael S. Tsirkin
2019-07-24 7:14 ` Peter Xu
2019-07-24 9:39 ` Michael S. Tsirkin
2019-07-24 10:03 ` Peter Xu
2019-07-24 14:43 ` Alex Williamson
2019-07-24 19:42 ` Alex Williamson
2019-07-25 14:34 ` Singh, Brijesh
2019-07-25 6:37 ` Peter Xu
2019-07-25 10:43 ` Michael S. Tsirkin
2019-07-25 14:00 ` Alex Williamson [this message]
2019-07-25 15:22 ` Michael S. Tsirkin
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=20190725080023.24de0d82@x1.home \
--to=alex.williamson@redhat.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=brijesh.singh@amd.com \
--cc=eric.auger@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhexu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.