From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Dong, Eric" <eric.dong@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Gao, Liming" <liming.gao@intel.com>, "Ni, Ruiyu" <ruiyu.ni@intel.com>
Subject: Re: [Patch 1/2] UefiCpuPkg: Add comments for PCDs definition.
Date: Wed, 9 Aug 2017 23:08:11 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5A7D761B7@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <20170809063207.19284-2-eric.dong@intel.com>
Eric,
Please add the default value settings to the detailed description.
For example, PcdCpuProcTraceMemSize should say that the default
value is 0x10 which disables the processor memory trace.
Also, the .uni file _HELP should contains the same information
as the detailed description, including the set of valid values
and their meanings. Please see
gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel in
MdePkg/MdePkg.uni for an example to follow.
Thanks,
Mike
> -----Original Message-----
> From: Dong, Eric
> Sent: Tuesday, August 8, 2017 11:32 PM
> To: edk2-devel@lists.01.org
> Cc: Gao, Liming <liming.gao@intel.com>; Ni, Ruiyu
> <ruiyu.ni@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: [Patch 1/2] UefiCpuPkg: Add comments for PCDs
> definition.
>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Eric Dong <eric.dong@intel.com>
> ---
> UefiCpuPkg/UefiCpuPkg.dec | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/UefiCpuPkg/UefiCpuPkg.dec
> b/UefiCpuPkg/UefiCpuPkg.dec
> index 2ddeab4..1f3a992 100644
> --- a/UefiCpuPkg/UefiCpuPkg.dec
> +++ b/UefiCpuPkg/UefiCpuPkg.dec
> @@ -287,10 +287,32 @@
>
> ## Contains the size of memory required when CPU processor
> trace is enabled.
> # @Prompt The memory size used for processor trace.
> + # 0x0: 4K,
> + # 0x1: 8K,
> + # 0x2: 16K,
> + # 0x3: 32K,
> + # 0x4: 64K,
> + # 0x5: 128K,
> + # 0x6: 256K,
> + # 0x7: 512K,
> + # 0x8: 1M,
> + # 0x9: 2M,
> + # 0xA: 4M,
> + # 0xB: 8M,
> + # 0xC: 16M,
> + # 0xD: 32M,
> + # 0xE: 64M,
> + # 0xF: 128M,
> + # 0x10: ProcTraceMemDisable
> + # @ValidRange 0x80000001 | 0 - 0x10
>
> gUefiCpuPkgTokenSpaceGuid.PcdCpuProcTraceMemSize|0x10|UINT32|0
> x60000012
>
> ## Contains the processor trace output scheme when CPU
> processor trace is enabled.
> # @Prompt The processor trace output scheme.
> + # 0: Single Range output scheme.<BR>
> + # 1: ToPA(Table of physical address) scheme.<BR>
> + # 2: Invalid scheme.<BR>
> + # @ValidRange 0x80000001 | 0 - 2
>
> gUefiCpuPkgTokenSpaceGuid.PcdCpuProcTraceOutputScheme|0x2|UINT
> 8|0x60000015
>
> [UserExtensions.TianoCore."ExtraFiles"]
> --
> 2.10.1.windows.1
next prev parent reply other threads:[~2017-08-09 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 6:32 [Patch 0/2] Add comments for new Pcds Eric Dong
2017-08-09 6:32 ` [Patch 1/2] UefiCpuPkg: Add comments for PCDs definition Eric Dong
2017-08-09 23:08 ` Kinney, Michael D [this message]
2017-08-09 6:32 ` [Patch 2/2] UefiCpuPkg UefiCpupkg.uni: Add new pcds comments Eric Dong
2017-08-09 11:15 ` [Patch 0/2] Add comments for new Pcds Laszlo Ersek
2017-08-09 12:23 ` Dong, Eric
-- strict thread matches above, loose matches on Subject: below --
2017-08-14 7:22 [Patch 0/2] Add comments for two new added Pcds Eric Dong
2017-08-14 7:22 ` [Patch 1/2] UefiCpuPkg: Add comments for PCDs definition Eric Dong
2017-08-16 15:58 ` Kinney, Michael D
2017-08-17 6:47 ` Dong, Eric
2017-08-17 7:55 ` Kinney, Michael D
2017-08-17 8:52 ` Dong, Eric
2017-08-17 17:39 ` Kinney, Michael D
[not found] ` <ED077930C258884BBCB450DB737E66224A9C366B@shsmsx102.ccr.corp.intel.com>
2017-08-22 22:30 ` Kinney, Michael D
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=E92EE9817A31E24EB0585FDF735412F5A7D761B7@ORSMSX113.amr.corp.intel.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