Re: [edk2] [PATCH 1/2] MdeModulePkg: Add PlatformAcpiLib LibraryClass.

2018-05-09 Thread Ni, Ruiyu 
I don't see much needs for a PlatformAcpiLib.
Platform can call AcpiTable protocol to install ACPI table itself.
The PlatformAcpiLib adds additional program interfaces but doesn't seem to be 
very helpful.

Any new program interfaces need to be carefully reviewed and only added when 
necessary.
Otherwise, people new to this project would be lost in many interfaces.

Thanks/Ray

> -Original Message-
> From: edk2-devel <edk2-devel-boun...@lists.01.org> On Behalf Of Marvin
> H?user
> Sent: Wednesday, May 9, 2018 11:38 PM
> To: edk2-devel@lists.01.org
> Cc: Ni, Ruiyu <ruiyu...@intel.com>; Dong, Eric <eric.d...@intel.com>; Yao,
> Jiewen <jiewen@intel.com>; Kinney, Michael D
> <michael.d.kin...@intel.com>; Laszlo Ersek <ler...@redhat.com>; Zeng,
> Star <star.z...@intel.com>
> Subject: Re: [edk2] [PATCH 1/2] MdeModulePkg: Add PlatformAcpiLib
> LibraryClass.
> 
> I continued to CC all people that were CC'd in Star's mail, even if I am not 
> sure
> if those are interested in this patch. If anyone doesn't want to be CC'd, I 
> will
> drop them of course.
> 
> Hey Star,
> 
> Indeed I expected it to be just for reference, however as most of the drivers
> you linked share the FV-loading code with AcpiPlatformDxe, having it
> "mainlined" makes sense to me.
> Especially as the "Intel platform forks" of this driver seem to all have a
> common memory leak which the sample driver does not have:
> https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Universal
> /Acpi/AcpiPlatformDxe/AcpiPlatform.c#L244
> If they were using the mainlined driver, the fix could be made once for
> MdeModulePkg and all other platforms would profit.
> Furthermore, I think it is a good idea to have the platform code not rely on
> where the tables come from (here FV), but instead just be requested to
> perform the required updates, not having to care about table origin,
> checksum fixup, etc.
> If I am not mistaken, all the additional platform code seen in those drivers
> can be implemented well via a library constructor.
> 
> Maybe the driver deserves a new name though, I'm not sure whether
> "AcpiPlatformDxe" is actually fitting.
> MinPlatform uses the "AcpiPlatform"  name to generate fundamental ACPI
> tables, while "BoardAcpiDxe" is the "AcpiPlatformDxe" + "PlatformAcpiLib"
> equivalent, if I am not mistaken.
> 
> Thanks in advance.
> 
> Best regards,
> Marvin
> 
> > -Original Message-
> > From: Zeng, Star <star.z...@intel.com>
> > Sent: Wednesday, May 9, 2018 11:33 AM
> > To: marvin.haeu...@outlook.com; edk2-devel@lists.01.org
> > Cc: Yao, Jiewen <jiewen@intel.com>; Kinney, Michael D
> > <michael.d.kin...@intel.com>; Laszlo Ersek (ler...@redhat.com)
> > <ler...@redhat.com>; Ni, Ruiyu <ruiyu...@intel.com>; Dong, Eric
> > <eric.d...@intel.com>; Zeng, Star <star.z...@intel.com>
> > Subject: RE: [PATCH 1/2] MdeModulePkg: Add PlatformAcpiLib LibraryClass.
> >
> > Marvin,
> >
> > It is good direction to reuse more code.
> > What am I concerning about are
> > 1. There are comments "Sample ACPI Platform Driver" in
> > AcpiPlatformDxe.inf and AcpiPlatformDxe.c, the current position of
> > AcpiPlatformDxe seems just for reference.
> > 2. Almost all the platforms have their own AcpiPlatformDxe, for
> > example
> >
> https://github.com/tianocore/edk2/tree/master/OvmfPkg/AcpiPlatformDxe
> >
> https://github.com/tianocore/edk2/tree/master/QuarkPlatformPkg/Acpi/Dx
> > e/AcpiPlatform
> > https://github.com/tianocore/edk2/tree/master/Vlv2TbltDevicePkg/AcpiPl
> > a
> > tform
> > ...
> >
> > Should more evaluation be done on them to see whether we can do more
> > or we just suggest platform should implement its own AcpiPlatformDxe?
> >
> > Including more experts.
> >
> >
> > Thanks,
> > Star
> > -Original Message-
> > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> > Marvin H?user
> > Sent: Wednesday, May 9, 2018 7:26 AM
> > To: edk2-devel@lists.01.org
> > Cc: Ni, Ruiyu <ruiyu...@intel.com>; Dong, Eric <eric.d...@intel.com>;
> > Zeng, Star <star.z...@intel.com>
> > Subject: [edk2] [PATCH 1/2] MdeModulePkg: Add PlatformAcpiLib
> > LibraryClass.
> >
> > PlatformAcpiLib can be consumed by the generic ACPI Platform driver to
> > allow platform specific updates to the ACPI tables loaded from the
> > configured Firmware Volume. This allows for more platforms to
> > incorporate the gener

Re: [edk2] [PATCH 1/2] MdeModulePkg: Add PlatformAcpiLib LibraryClass.

2018-05-09 Thread Laszlo Ersek 
Hi,

On 05/09/18 11:32, Zeng, Star wrote:
> Marvin,
> 
> It is good direction to reuse more code.
> What am I concerning about are
> 1. There are comments "Sample ACPI Platform Driver" in AcpiPlatformDxe.inf 
> and AcpiPlatformDxe.c, the current position of AcpiPlatformDxe seems just for 
> reference.
> 2. Almost all the platforms have their own AcpiPlatformDxe, for example
> https://github.com/tianocore/edk2/tree/master/OvmfPkg/AcpiPlatformDxe
> https://github.com/tianocore/edk2/tree/master/QuarkPlatformPkg/Acpi/Dxe/AcpiPlatform
> https://github.com/tianocore/edk2/tree/master/Vlv2TbltDevicePkg/AcpiPlatform
> ...
> 
> Should more evaluation be done on them to see whether we can do more or we 
> just suggest platform should implement its own AcpiPlatformDxe?
> 
> Including more experts.

I can't really comment on other platforms, but for OvmfPkg and
ArmVirtPkg, the ACPI platform driver(s) are totally custom. The ACPI
payload is generated by VMM software (on the host), the driver loads the
blobs and processes them in various ways (also controlled by the VMM),
and finally the driver installs the tables.

Marvin writes below:

> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Marvin 
> H?user
> Sent: Wednesday, May 9, 2018 7:26 AM
> To: edk2-devel@lists.01.org
> Cc: Ni, Ruiyu ; Dong, Eric ; Zeng, 
> Star 
> Subject: [edk2] [PATCH 1/2] MdeModulePkg: Add PlatformAcpiLib LibraryClass.
> 
> PlatformAcpiLib can be consumed by the generic ACPI Platform driver
> to allow platform specific updates to the ACPI tables loaded from the
> configured Firmware Volume.

In our use case, the ACPI tables are not loaded from firmware volumes at
all. (OVMF still has such a fallback for extremely old QEMU versions,
but that fallback should rather be removed than modified in any way.)

Thanks,
Laszlo

> This allows for more platforms to
> incorporate the generic ACPI Platform driver.
> 
> This commit also provides a NULL implementation of PlatformAcpiLib.
> 
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Marvin Haeuser 
> ---
>  MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.c   | 
> 36 
>  MdeModulePkg/Include/Library/PlatformAcpiLib.h   | 
> 36 
>  MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.inf | 
> 35 +++
>  MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.uni | 
> 18 ++
>  MdeModulePkg/MdeModulePkg.dec|  
> 4 +++
>  MdeModulePkg/MdeModulePkg.dsc|  
> 2 ++
>  6 files changed, 131 insertions(+)
> 
> diff --git 
> a/MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.c 
> b/MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.c
> new file mode 100644
> index ..5d5d0d051e1b
> --- /dev/null
> +++ b/MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.c
> @@ -0,0 +1,36 @@
> +/** @file
> +  Null Platform ACPI Library instance.
> +
> +Copyright (c) 2018, Intel Corporation. All rights reserved.
> +This program and the accompanying materials are licensed and made available 
> under 
> +the terms and conditions of the BSD License that accompanies this 
> distribution.  
> +The full text of the license may be found at
> +http://opensource.org/licenses/bsd-license.php.  
>   
> +
> +THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,
>  
> +WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
> +
> +**/
> +
> +#include 
> +
> +#include 
> +
> +/**
> +  Performs platform specific updates to CurrentTable.
> +
> +  @param[in,out] CurrentTable  The table to perform updates on.
> +
> +  @retval RETURN_SUCCESS  The platform specific ACPI table updates were 
> applied
> +  successfully.
> +  @retval other   The platform specific ACPI table updates could not 
> be
> +  applied.
> +  
> +**/
> +RETURN_STATUS
> +PlatformAcpiUpdateTable (
> +  IN OUT EFI_ACPI_COMMON_HEADER  *CurrentTable
> +  )
> +{
> +  return RETURN_SUCCESS;
> +}
> diff --git a/MdeModulePkg/Include/Library/PlatformAcpiLib.h 
> b/MdeModulePkg/Include/Library/PlatformAcpiLib.h
> new file mode 100644
> index ..a3e367f3ab61
> --- /dev/null
> +++ b/MdeModulePkg/Include/Library/PlatformAcpiLib.h
> @@ -0,0 +1,36 @@
> +/** @file
> +  Platform ACPI library. Platform can provide an implementation of this
> +  library class to provide an ACPI table update routine that may be required
> +  for some type of platform initialization.
> +
> +Copyright (c) 2018, Intel Corporation. All rights reserved.
> +This program and the accompanying materials are licensed and

Re: [edk2] [PATCH 1/2] MdeModulePkg: Add PlatformAcpiLib LibraryClass.

2018-05-09 Thread Zeng, Star 
Marvin,

It is good direction to reuse more code.
What am I concerning about are
1. There are comments "Sample ACPI Platform Driver" in AcpiPlatformDxe.inf and 
AcpiPlatformDxe.c, the current position of AcpiPlatformDxe seems just for 
reference.
2. Almost all the platforms have their own AcpiPlatformDxe, for example
https://github.com/tianocore/edk2/tree/master/OvmfPkg/AcpiPlatformDxe
https://github.com/tianocore/edk2/tree/master/QuarkPlatformPkg/Acpi/Dxe/AcpiPlatform
https://github.com/tianocore/edk2/tree/master/Vlv2TbltDevicePkg/AcpiPlatform
...

Should more evaluation be done on them to see whether we can do more or we just 
suggest platform should implement its own AcpiPlatformDxe?

Including more experts.


Thanks,
Star
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Marvin 
H?user
Sent: Wednesday, May 9, 2018 7:26 AM
To: edk2-devel@lists.01.org
Cc: Ni, Ruiyu ; Dong, Eric ; Zeng, 
Star 
Subject: [edk2] [PATCH 1/2] MdeModulePkg: Add PlatformAcpiLib LibraryClass.

PlatformAcpiLib can be consumed by the generic ACPI Platform driver
to allow platform specific updates to the ACPI tables loaded from the
configured Firmware Volume. This allows for more platforms to
incorporate the generic ACPI Platform driver.

This commit also provides a NULL implementation of PlatformAcpiLib.

Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Marvin Haeuser 
---
 MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.c   | 36 

 MdeModulePkg/Include/Library/PlatformAcpiLib.h   | 36 

 MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.inf | 35 
+++
 MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.uni | 18 
++
 MdeModulePkg/MdeModulePkg.dec|  4 
+++
 MdeModulePkg/MdeModulePkg.dsc|  2 
++
 6 files changed, 131 insertions(+)

diff --git 
a/MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.c 
b/MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.c
new file mode 100644
index ..5d5d0d051e1b
--- /dev/null
+++ b/MdeModulePkg/Library/BasePlatformAcpiLibNull/BasePlatformAcpiLibNull.c
@@ -0,0 +1,36 @@
+/** @file
+  Null Platform ACPI Library instance.
+
+Copyright (c) 2018, Intel Corporation. All rights reserved.
+This program and the accompanying materials are licensed and made available 
under 
+the terms and conditions of the BSD License that accompanies this 
distribution.  
+The full text of the license may be found at
+http://opensource.org/licenses/bsd-license.php.

+
+THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,  
   
+WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
+
+**/
+
+#include 
+
+#include 
+
+/**
+  Performs platform specific updates to CurrentTable.
+
+  @param[in,out] CurrentTable  The table to perform updates on.
+
+  @retval RETURN_SUCCESS  The platform specific ACPI table updates were applied
+  successfully.
+  @retval other   The platform specific ACPI table updates could not be
+  applied.
+  
+**/
+RETURN_STATUS
+PlatformAcpiUpdateTable (
+  IN OUT EFI_ACPI_COMMON_HEADER  *CurrentTable
+  )
+{
+  return RETURN_SUCCESS;
+}
diff --git a/MdeModulePkg/Include/Library/PlatformAcpiLib.h 
b/MdeModulePkg/Include/Library/PlatformAcpiLib.h
new file mode 100644
index ..a3e367f3ab61
--- /dev/null
+++ b/MdeModulePkg/Include/Library/PlatformAcpiLib.h
@@ -0,0 +1,36 @@
+/** @file
+  Platform ACPI library. Platform can provide an implementation of this
+  library class to provide an ACPI table update routine that may be required
+  for some type of platform initialization.
+
+Copyright (c) 2018, Intel Corporation. All rights reserved.
+This program and the accompanying materials are licensed and made available 
under 
+the terms and conditions of the BSD License that accompanies this 
distribution.  
+The full text of the license may be found at
+http://opensource.org/licenses/bsd-license.php.

+
+THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,  
   
+WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
+
+**/
+
+#ifndef __PLATFORM_ACPI_LIB__
+#define __PLATFORM_ACPI_LIB__
+
+/**
+  Performs platform specific updates to CurrentTable.
+
+  @param[in,out] CurrentTable  The table to perform updates on.
+
+  @retval RETURN_SUCCESS  The platform specific ACPI table updates were applied
+  successfully.
+  @retval other   The platform specific ACPI table updates could not be
+