public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Ni, Ray" <ray.ni@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	 "tigerliu@zhaoxin.com" <tigerliu@zhaoxin.com>,
	Michael Kinney <michael.d.kinney@intel.com>,
	 "Leif Lindholm (Nuvia address)" <leif@nuviainc.com>,
	Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] Questions about UEFI MAT / PcdPropertiesTableEnable
Date: Wed, 25 Mar 2020 18:00:39 +0100	[thread overview]
Message-ID: <CAKv+Gu-=vyokQaT6zTcB-QWtdKcO=s5JQsXcM6yvVSoMCXXq3Q@mail.gmail.com> (raw)
In-Reply-To: <d22b90b3-3272-e057-a8fe-87c7957c19ec@redhat.com>

On Wed, 25 Mar 2020 at 17:55, Laszlo Ersek <lersek@redhat.com> wrote:
>
> On 03/25/20 06:17, Ni, Ray wrote:
> >>
> >> The properties table should not be used. It has been superseded by the memory attributes table, per spec.
> >>
> >> In edk2, the properties table is controlled by the PCD, regardless of the memory attributes table.
> >>
> >> In edk2, the memory attributes table is always produced, regardless of the properties table.
> >>
> >> Please see the discussion under:
> >>
> >> [edk2] [patch 0/7] Add UEFI2.6 MemoryAttributesTable support.
> >> http://mid.mail-archive.com/1454069539-4056-1-git-send-email-jiewen.yao@intel.com
> >>
> >
...
>
> > Do you think we could remove properties table?
>
> Yes, that's exactly what Ard requested, as soon as Jiewen posted the MAT
> series. Back then, Jiewen said that some production OSes were still
> using the properties table, and would need time to migrate to MAT.
>
> The agreement -- four years ago! -- seemed to be that the UEFI spec
> should drop the properties table definition in some time, and then edk2
> could remove the reference implementation too.
>
> See the attached discussion.
>
> Given that the properties table had been deprecated in the UEFI spec
> even in Feb 2016, I think it's now high time to remove it altogether
> (both spec and edk2).
>
> > The existence of both is confusing.
>
> Yes, very much.
>

Agreed. We should at least log this as a task, and if anyone has the
bandwidth to do the work, plan it for the next stable tag.

  reply	other threads:[~2020-03-25 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17  9:27 [edk2-devel] Questions about UEFI MAT / PcdPropertiesTableEnable Tiger Liu(BJ-RD)
2020-03-23 13:21 ` Laszlo Ersek
2020-03-25  5:17   ` Ni, Ray
2020-03-25 16:54     ` Laszlo Ersek
2020-03-25 17:00       ` Ard Biesheuvel [this message]
2020-03-25 20:34         ` [EXTERNAL] " Bret Barkelew
  -- strict thread matches above, loose matches on Subject: below --
2020-03-25  3:36 Tiger Liu(BJ-RD)

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-list 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='CAKv+Gu-=vyokQaT6zTcB-QWtdKcO=s5JQsXcM6yvVSoMCXXq3Q@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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