All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jacob Pan (Jun)" <jacob.jun.pan@intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
	kevin.tian@intel.com, "Rothman,
	 Michael A" <michael.a.rothman@intel.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	linux-pci@vger.kernel.org, jasowang@redhat.com, "Kaneda,
	Erik" <erik.kaneda@intel.com>,
	virtualization@lists.linux-foundation.org,
	iommu@lists.linux-foundation.org, sebastien.boeuf@intel.com,
	jacob.jun.pan@intel.com, bhelgaas@google.com,
	robin.murphy@arm.com
Subject: Re: [PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
Date: Wed, 4 Mar 2020 13:37:44 -0800	[thread overview]
Message-ID: <20200304133744.00000fdb@intel.com> (raw)
In-Reply-To: <20200304174045.GC3315@8bytes.org>

On Wed, 4 Mar 2020 18:40:46 +0100
Joerg Roedel <joro@8bytes.org> wrote:

> On Wed, Mar 04, 2020 at 04:38:21PM +0100, Jean-Philippe Brucker wrote:
> > I agree with this. The problem is I don't know how to get a new
> > ACPI table or change an existing one. It needs to go through the
> > UEFI forum in order to be accepted, and I don't have any weight
> > there. I've been trying to get the tiny change into IORT for ages.
> > I haven't been given any convincing reason against it or offered
> > any alternative, it's just stalled. The topology description
> > introduced here wasn't my first choice either but unless someone
> > can help finding another way into ACPI, I don't have a better
> > idea.  
> 
> A quote from the ACPI Specification (Version 6.3, Section 5.2.6,
> Page 119):
> 
> 	Table signatures will be reserved by the ACPI promoters and
> 	posted independently of this specification in ACPI errata and
> 	clarification documents on the ACPI web site. Requests to
> 	reserve a 4-byte alphanumeric table signature should be sent
> to the email address info@acpi.info and should include the purpose
> 	of the table and reference URL to a document that describes
> the table format. Tables defined outside of the ACPI specification
> 	may define data value encodings in either little endian or big
> 	endian format. For the purpose of clarity, external table
> 	definition documents should include the endian-ness of their
> 	data value encodings.
> 
> So it sounds like you need to specifiy the table format and send a
> request to info@acpi.info to get a table signature for it.
> 
+ Mike and Erik who work closely on UEFI and ACPICA.

Copy paste Erik's initial response below on how to get a new table,
seems to confirm with the process you stated above.

"Fairly easy. You reserve a 4-letter symbol by sending a message
requesting to reserve the signature to Mike or the ASWG mailing list or
info@acpi.info

There is also another option. You can have ASWG own this new table so
that not one entity or company owns the new table."

> Regards,
> 
> 	Joerg

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: "Jacob Pan (Jun)" <jacob.jun.pan@intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Auger Eric <eric.auger@redhat.com>,
	<iommu@lists.linux-foundation.org>,
	<virtualization@lists.linux-foundation.org>,
	<linux-pci@vger.kernel.org>, <bhelgaas@google.com>,
	<jasowang@redhat.com>, <kevin.tian@intel.com>,
	<sebastien.boeuf@intel.com>, <robin.murphy@arm.com>,
	jacob.jun.pan@intel.com, "Kaneda, Erik" <erik.kaneda@intel.com>,
	"Rothman, Michael A" <michael.a.rothman@intel.com>
Subject: Re: [PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
Date: Wed, 4 Mar 2020 13:37:44 -0800	[thread overview]
Message-ID: <20200304133744.00000fdb@intel.com> (raw)
In-Reply-To: <20200304174045.GC3315@8bytes.org>

On Wed, 4 Mar 2020 18:40:46 +0100
Joerg Roedel <joro@8bytes.org> wrote:

> On Wed, Mar 04, 2020 at 04:38:21PM +0100, Jean-Philippe Brucker wrote:
> > I agree with this. The problem is I don't know how to get a new
> > ACPI table or change an existing one. It needs to go through the
> > UEFI forum in order to be accepted, and I don't have any weight
> > there. I've been trying to get the tiny change into IORT for ages.
> > I haven't been given any convincing reason against it or offered
> > any alternative, it's just stalled. The topology description
> > introduced here wasn't my first choice either but unless someone
> > can help finding another way into ACPI, I don't have a better
> > idea.  
> 
> A quote from the ACPI Specification (Version 6.3, Section 5.2.6,
> Page 119):
> 
> 	Table signatures will be reserved by the ACPI promoters and
> 	posted independently of this specification in ACPI errata and
> 	clarification documents on the ACPI web site. Requests to
> 	reserve a 4-byte alphanumeric table signature should be sent
> to the email address info@acpi.info and should include the purpose
> 	of the table and reference URL to a document that describes
> the table format. Tables defined outside of the ACPI specification
> 	may define data value encodings in either little endian or big
> 	endian format. For the purpose of clarity, external table
> 	definition documents should include the endian-ness of their
> 	data value encodings.
> 
> So it sounds like you need to specifiy the table format and send a
> request to info@acpi.info to get a table signature for it.
> 
+ Mike and Erik who work closely on UEFI and ACPICA.

Copy paste Erik's initial response below on how to get a new table,
seems to confirm with the process you stated above.

"Fairly easy. You reserve a 4-letter symbol by sending a message
requesting to reserve the signature to Mike or the ASWG mailing list or
info@acpi.info

There is also another option. You can have ASWG own this new table so
that not one entity or company owns the new table."

> Regards,
> 
> 	Joerg


WARNING: multiple messages have this Message-ID (diff)
From: "Jacob Pan (Jun)" <jacob.jun.pan@intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Auger Eric <eric.auger@redhat.com>,
	iommu@lists.linux-foundation.org,
	virtualization@lists.linux-foundation.org,
	linux-pci@vger.kernel.org, bhelgaas@google.com,
	jasowang@redhat.com, kevin.tian@intel.com,
	sebastien.boeuf@intel.com, robin.murphy@arm.com,
	jacob.jun.pan@intel.com, "Kaneda, Erik" <erik.kaneda@intel.com>,
	"Rothman, Michael A" <michael.a.rothman@intel.com>
Subject: Re: [PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
Date: Wed, 4 Mar 2020 13:37:44 -0800	[thread overview]
Message-ID: <20200304133744.00000fdb@intel.com> (raw)
In-Reply-To: <20200304174045.GC3315@8bytes.org>

On Wed, 4 Mar 2020 18:40:46 +0100
Joerg Roedel <joro@8bytes.org> wrote:

> On Wed, Mar 04, 2020 at 04:38:21PM +0100, Jean-Philippe Brucker wrote:
> > I agree with this. The problem is I don't know how to get a new
> > ACPI table or change an existing one. It needs to go through the
> > UEFI forum in order to be accepted, and I don't have any weight
> > there. I've been trying to get the tiny change into IORT for ages.
> > I haven't been given any convincing reason against it or offered
> > any alternative, it's just stalled. The topology description
> > introduced here wasn't my first choice either but unless someone
> > can help finding another way into ACPI, I don't have a better
> > idea.  
> 
> A quote from the ACPI Specification (Version 6.3, Section 5.2.6,
> Page 119):
> 
> 	Table signatures will be reserved by the ACPI promoters and
> 	posted independently of this specification in ACPI errata and
> 	clarification documents on the ACPI web site. Requests to
> 	reserve a 4-byte alphanumeric table signature should be sent
> to the email address info@acpi.info and should include the purpose
> 	of the table and reference URL to a document that describes
> the table format. Tables defined outside of the ACPI specification
> 	may define data value encodings in either little endian or big
> 	endian format. For the purpose of clarity, external table
> 	definition documents should include the endian-ness of their
> 	data value encodings.
> 
> So it sounds like you need to specifiy the table format and send a
> request to info@acpi.info to get a table signature for it.
> 
+ Mike and Erik who work closely on UEFI and ACPICA.

Copy paste Erik's initial response below on how to get a new table,
seems to confirm with the process you stated above.

"Fairly easy. You reserve a 4-letter symbol by sending a message
requesting to reserve the signature to Mike or the ASWG mailing list or
info@acpi.info

There is also another option. You can have ASWG own this new table so
that not one entity or company owns the new table."

> Regards,
> 
> 	Joerg

  reply	other threads:[~2020-03-04 21:37 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28 17:25 [PATCH v2 0/3] virtio-iommu on x86 and non-devicetree platforms Jean-Philippe Brucker
2020-02-28 17:25 ` Jean-Philippe Brucker
2020-02-28 17:25 ` [PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space Jean-Philippe Brucker
2020-02-28 17:25   ` Jean-Philippe Brucker
2020-03-01 11:17   ` Michael S. Tsirkin
2020-03-01 11:17     ` Michael S. Tsirkin
2020-03-02 16:16   ` Joerg Roedel
2020-03-02 16:16     ` Joerg Roedel
2020-03-03 10:19     ` Auger Eric
2020-03-03 10:19       ` Auger Eric
2020-03-03 13:01       ` Joerg Roedel
2020-03-03 13:01         ` Joerg Roedel
2020-03-03 14:00         ` Michael S. Tsirkin
2020-03-03 14:00           ` Michael S. Tsirkin
2020-03-03 15:53           ` Joerg Roedel
2020-03-03 15:53             ` Joerg Roedel
2020-03-03 16:09             ` Michael S. Tsirkin
2020-03-03 16:09               ` Michael S. Tsirkin
2020-03-03 16:21               ` Auger Eric
2020-03-03 16:21                 ` Auger Eric
2020-03-04 13:37               ` Joerg Roedel
2020-03-04 13:37                 ` Joerg Roedel
2020-03-04 15:38                 ` Jean-Philippe Brucker
2020-03-04 15:38                   ` Jean-Philippe Brucker
2020-03-04 17:40                   ` Joerg Roedel
2020-03-04 17:40                     ` Joerg Roedel
2020-03-04 21:37                     ` Jacob Pan (Jun) [this message]
2020-03-04 21:37                       ` Jacob Pan (Jun)
2020-03-04 21:37                       ` Jacob Pan (Jun)
2020-03-04 21:54                       ` Joerg Roedel
2020-03-04 21:54                         ` Joerg Roedel
2020-03-05 15:42                         ` Michael S. Tsirkin
2020-03-05 15:42                           ` Michael S. Tsirkin
2020-03-04 15:48                 ` Jacob Pan
2020-03-04 15:48                   ` Jacob Pan
2020-03-04 17:34                   ` Joerg Roedel
2020-03-04 17:34                     ` Joerg Roedel
2020-03-04 19:34                 ` Michael S. Tsirkin
2020-03-04 19:34                   ` Michael S. Tsirkin
2020-03-04 21:50                   ` Joerg Roedel
2020-03-04 21:50                     ` Joerg Roedel
2020-03-05 15:39                     ` Michael S. Tsirkin
2020-03-05 15:39                       ` Michael S. Tsirkin
2020-03-03 14:02     ` Michael S. Tsirkin
2020-03-03 14:02       ` Michael S. Tsirkin
2020-03-03 14:02       ` Michael S. Tsirkin
2020-03-05  8:07   ` Tian, Kevin
2020-03-05  8:07     ` Tian, Kevin
2020-03-11 17:48     ` Jean-Philippe Brucker
2020-03-11 17:48       ` Jean-Philippe Brucker
2020-03-11 21:48       ` Michael S. Tsirkin
2020-03-11 21:48         ` Michael S. Tsirkin
2020-04-13 13:22   ` Michael S. Tsirkin
2020-04-13 13:22     ` Michael S. Tsirkin
2020-04-21  7:31   ` Tian, Kevin
2020-04-21  7:31     ` Tian, Kevin
2020-08-21  8:39     ` Jean-Philippe Brucker
2020-08-21  8:39       ` Jean-Philippe Brucker
2020-08-21  8:39       ` Jean-Philippe Brucker
2020-02-28 17:25 ` [PATCH v2 2/3] PCI: Add DMA configuration for virtual platforms Jean-Philippe Brucker
2020-02-28 17:25   ` Jean-Philippe Brucker
2020-03-18 21:10   ` Bjorn Helgaas
2020-03-18 21:10     ` Bjorn Helgaas
2020-02-28 17:25 ` [PATCH v2 3/3] iommu/virtio: Enable x86 support Jean-Philippe Brucker
2020-02-28 17:25   ` Jean-Philippe Brucker
2020-02-29 14:23   ` kbuild test robot
2020-02-29 14:23     ` kbuild test robot
2020-02-29 14:23     ` kbuild test robot

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=20200304133744.00000fdb@intel.com \
    --to=jacob.jun.pan@intel.com \
    --cc=bhelgaas@google.com \
    --cc=erik.kaneda@intel.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=michael.a.rothman@intel.com \
    --cc=mst@redhat.com \
    --cc=robin.murphy@arm.com \
    --cc=sebastien.boeuf@intel.com \
    --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 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.