public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yoshinoya" <yoshinoyatoko@163.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] Is DEBUG output function safe for MP case?
Date: Fri, 31 May 2024 14:22:28 +0800 (CST)	[thread overview]
Message-ID: <2d8e2935.5b57.18fcd506481.Coremail.yoshinoyatoko@163.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 587 bytes --]

Hello
I ask for help for debug output in multi-core case.


Is the current DEBUG marco safe for AP Cores to output message?
If the output message is too long, it takes too much time, will it cause some abnormal exception?


Thanks

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119406): https://edk2.groups.io/g/devel/message/119406
Mute This Topic: https://groups.io/mt/106403315/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 1254 bytes --]

             reply	other threads:[~2024-05-31  6:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31  6:22 Yoshinoya [this message]
2024-05-31  6:33 ` 回复: [edk2-devel] Is DEBUG output function safe for MP case? Jeff Fan via groups.io
2024-05-31  9:59   ` Andrew Fish via groups.io
     [not found]   ` <17D48A6E78A3E42F.21428@groups.io>
2024-05-31 10:14     ` Andrew Fish via groups.io
2024-06-03  8:24   ` 回复: " Yoshinoya
2024-06-04  1:11     ` 回复: " Jeff Fan via groups.io
2024-06-06  4:57       ` Yoshinoya
     [not found]       ` <17D65170E6B4AF25.31248@groups.io>
2024-06-12  4:42         ` [edk2-devel] processing compressed section during CAR phase Yoshinoya
2024-06-20  8:56           ` [edk2-devel] uncompress peims during car phase Yoshinoya
2024-06-06  4:55 ` [edk2-devel] pci command supports CXL device type Yoshinoya

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=2d8e2935.5b57.18fcd506481.Coremail.yoshinoyatoko@163.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