public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Dong, Eric" <eric.dong@intel.com>
To: "Ni, Ray" <ray.ni@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Patch 0/2] UefiCpuPkg: Default avoid print.
Date: Thu, 1 Aug 2019 09:07:58 +0000	[thread overview]
Message-ID: <ED077930C258884BBCB450DB737E662259EB8076@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5C26764D@SHSMSX104.ccr.corp.intel.com>

Hi Ray,

Yes, I will remove debug code in v2 change.

I have submitted feature request for new MP safe DebugLib:
https://bugzilla.tianocore.org/show_bug.cgi?id=2043.


Thanks,
Eric
> -----Original Message-----
> From: Ni, Ray
> Sent: Thursday, August 1, 2019 3:52 PM
> To: Dong, Eric <eric.dong@intel.com>; devel@edk2.groups.io
> Cc: Laszlo Ersek <lersek@redhat.com>
> Subject: RE: [Patch 0/2] UefiCpuPkg: Default avoid print.
> 
> Eric,
> My understanding to your patch is you want to avoid printing from AP
> because some platforms may choose wrong DebugLib instance for the
> CpuFeaturePei/Dxe driver, which leads to system hang.
> To make the platform happy and while the value of printing the debug
> message is less, the solution in your patch is to suppress the debug message
> unless a minor code change is made to turn on the debugging.
> 
> Given that there are many comments/suggestions on how to implement a
> MP safe debugging infra, I don't think implementing such a MP safe
> debugging infra can be quickly done.
> 
> How about directly remove the debug message instead of disabling in your
> V2 patch?
> 
> The goal of MP safe debugging infra is to provide a mechanism to print debug
> message in MP environment that doesn't depend on platform DSC library
> instance mapping.
> 
> Can you please submit a BZ to capture that and also remember to attach the
> URL to this mail thread in BZ?
> 
> We could use future TianoCore Design Meeting to discuss about this.
> 
> Thanks,
> Ray
> 
> 
> > -----Original Message-----
> > From: Dong, Eric
> > Sent: Wednesday, July 31, 2019 3:35 PM
> > To: devel@edk2.groups.io
> > Cc: Ni, Ray <ray.ni@intel.com>; Laszlo Ersek <lersek@redhat.com>
> > Subject: [Patch 0/2] UefiCpuPkg: Default avoid print.
> >
> > REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1984
> >
> > Current debug message brings much restriction for the platform which
> > use this driver.
> >
> > For PEI and DXE phase, platform mush link base DebugLib (without using
> > any pei/dxe services, even for its dependent libraries).
> >
> > This patch default disable this debug message, only open it when need
> > to debug the related code.
> >
> > Signed-off-by: Eric Dong <eric.dong@intel.com>
> > Cc: Ray Ni <ray.ni@intel.com>
> > Cc: Laszlo Ersek <lersek@redhat.com>
> >
> > Eric Dong (2):
> >   UefiCpuPkg/RegisterCpuFeaturesLib: Default avoid print.
> >   UefiCpuPkg/PiSmmCpuDxeSmm: Default avoid print.
> >
> >  .../Library/RegisterCpuFeaturesLib/CpuFeaturesInitialize.c    | 4 +++-
> >  UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c                             | 4 +++-
> >  2 files changed, 6 insertions(+), 2 deletions(-)
> >
> > --
> > 2.21.0.windows.1


      reply	other threads:[~2019-08-01  9:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31  7:35 [Patch 0/2] UefiCpuPkg: Default avoid print Dong, Eric
2019-07-31  7:35 ` [Patch 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: " Dong, Eric
2019-07-31  7:35 ` [Patch 2/2] UefiCpuPkg/PiSmmCpuDxeSmm: " Dong, Eric
2019-07-31 12:43 ` [Patch 0/2] UefiCpuPkg: " Laszlo Ersek
2019-07-31 16:34   ` [edk2-devel] " Brian J. Johnson
2019-07-31 18:06     ` Andrew Fish
2019-07-31 18:58     ` Laszlo Ersek
2019-07-31 22:04       ` Johnson, Michael
2019-08-02  0:12         ` Laszlo Ersek
2019-08-01 20:20       ` Brian J. Johnson
2019-08-01 21:14         ` Andrew Fish
2019-08-02 21:45           ` Laszlo Ersek
2019-08-01  7:51 ` Ni, Ray
2019-08-01  9:07   ` Dong, Eric [this message]

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=ED077930C258884BBCB450DB737E662259EB8076@shsmsx102.ccr.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