From: "Michael S. Tsirkin" <mst@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Auger Eric <eric.auger@redhat.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
iommu@lists.linux-foundation.org,
virtualization@lists.linux-foundation.org,
virtio-dev@lists.oasis-open.org, linux-pci@vger.kernel.org,
bhelgaas@google.com, jasowang@redhat.com, kevin.tian@intel.com,
sebastien.boeuf@intel.com, lorenzo.pieralisi@arm.com
Subject: [virtio-dev] Re: [PATCH v3 0/6] Add virtio-iommu built-in topology
Date: Fri, 25 Sep 2020 06:22:20 -0400 [thread overview]
Message-ID: <20200925062122-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200924125046.GR27174@8bytes.org>
On Thu, Sep 24, 2020 at 02:50:46PM +0200, Joerg Roedel wrote:
> On Thu, Sep 24, 2020 at 08:41:21AM -0400, Michael S. Tsirkin wrote:
> > But this has nothing to do with Linux. There is also no guarantee that
> > the two committees will decide to use exactly the same format. Once one
> > of them sets the format in stone, we can add support for that format to
> > linux. If another one is playing nice and uses the same format, we can
> > use the same parsers. If it doesn't linux will have to follow suit.
>
> Or Linux decides to support only one of the formats, which would then be
> ACPI.
>
> Regards,
>
> Joerg
It's really up to hypervisors not guests, linux as a guest can for sure
refuse to work somewhere, but that's normally not very attractive.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2020-09-25 10:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 13:15 [virtio-dev] [PATCH v3 0/6] Add virtio-iommu built-in topology Jean-Philippe Brucker
2020-08-21 13:15 ` [virtio-dev] [PATCH v3 1/6] iommu/virtio: Move to drivers/iommu/virtio/ Jean-Philippe Brucker
2020-09-04 15:29 ` [virtio-dev] " Auger Eric
2020-08-21 13:15 ` [virtio-dev] [PATCH v3 2/6] iommu/virtio: Add topology helpers Jean-Philippe Brucker
2020-09-04 16:22 ` [virtio-dev] " Auger Eric
2020-09-24 8:31 ` Jean-Philippe Brucker
2020-08-21 13:15 ` [virtio-dev] [PATCH v3 3/6] PCI: Add DMA configuration for virtual platforms Jean-Philippe Brucker
2020-08-21 13:15 ` [virtio-dev] [PATCH v3 4/6] iommu/virtio: Add topology definitions Jean-Philippe Brucker
2020-09-04 15:30 ` [virtio-dev] " Auger Eric
2020-08-21 13:15 ` [virtio-dev] [PATCH v3 5/6] iommu/virtio: Support topology description in config space Jean-Philippe Brucker
2020-09-04 16:05 ` [virtio-dev] " Auger Eric
2020-09-24 8:33 ` Jean-Philippe Brucker
[not found] ` <20200924152203.GA2320481@bjorn-Precision-5520>
2020-09-25 8:12 ` Jean-Philippe Brucker
2020-08-21 13:15 ` [virtio-dev] [PATCH v3 6/6] iommu/virtio: Enable x86 support Jean-Philippe Brucker
2020-08-26 13:26 ` [virtio-dev] Re: [PATCH v3 0/6] Add virtio-iommu built-in topology Michael S. Tsirkin
2020-08-27 8:01 ` Jean-Philippe Brucker
2020-09-04 16:24 ` Auger Eric
2020-09-24 9:00 ` Michael S. Tsirkin
[not found] ` <20200924092129.GH27174@8bytes.org>
2020-09-24 9:38 ` Michael S. Tsirkin
2020-09-24 9:54 ` Auger Eric
[not found] ` <20201002182348.GO138842@redhat.com>
2020-10-06 15:23 ` Auger Eric
[not found] ` <20201103200904.GA1557194@redhat.com>
2020-11-04 9:33 ` Jean-Philippe Brucker
[not found] ` <20200924100255.GM27174@8bytes.org>
2020-09-24 10:24 ` Gerd Hoffmann
2020-09-24 10:29 ` Jean-Philippe Brucker
2020-09-24 12:41 ` Michael S. Tsirkin
[not found] ` <20200924125046.GR27174@8bytes.org>
2020-09-25 10:22 ` Michael S. Tsirkin [this message]
2020-09-25 8:48 ` Jean-Philippe Brucker
2020-09-25 10:22 ` Michael S. Tsirkin
2020-09-25 11:26 ` Jean-Philippe Brucker
2020-09-25 13:44 ` Michael S. Tsirkin
2020-09-25 14:14 ` Gerd Hoffmann
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=20200925062122-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bhelgaas@google.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jasowang@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sebastien.boeuf@intel.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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