public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kun Qin via groups.io" <Kun.Qin=microsoft.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] Proposing v3 of MM communicate buffer
Date: Wed, 7 Aug 2024 18:14:49 +0000	[thread overview]
Message-ID: <BL1PR21MB3160D99BE89B67E601F184C2E9B82@BL1PR21MB3160.namprd21.prod.outlook.com> (raw)

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

Hi all,

I am trying to propose a change into PI spec and would like to gather some feedback in this forum.

Essentially, the current communicate header contains a UINTN field in place, which is causing programing
errors when trying to communicate the message between different operation mode (i.e. PEI in IA32
communicate into MM in x64). There are various implementations at large to compensate for this
size discrepancy through the edk2 codebase, thus fixing the existing communicate buffer definition
will be less feasible. Thus I think proposing a new structure and implement the corresponding header
parser will be a simpler approach, which also allows a bit more flexibility to inject new features/checks
into the communication channel.

The proposed change for the spec is detailed here:
https://github.com/kuqin12/edk2/blob/BZ3398-MmCommunicate-Length-v4/CodeFirst/BZ3430-SpecChange.md

And the code first change is listed here:
https://github.com/kuqin12/edk2/blob/BZ3398-MmCommunicate-Length-v4/

Could you please provide me with any feedback that you think might be helpful for future usage of MM
communicate? Any input is appreciated.

Regards,
Kun



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120286): https://edk2.groups.io/g/devel/message/120286
Mute This Topic: https://groups.io/mt/107775882/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: 6539 bytes --]

             reply	other threads:[~2024-08-07 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 18:14 Kun Qin via groups.io [this message]
2024-08-07 20:25 ` [edk2-devel] Proposing v3 of MM communicate buffer Kun Qin via groups.io
2024-08-08  8:14 ` Ni, Ray
2024-08-08 17:41   ` Kun Qin via groups.io
2024-08-09  3:47     ` Ni, Ray
2024-08-09  7:58       ` Kun Qin via groups.io
2024-08-12  5:50         ` Ni, Ray
2024-08-12 19:07           ` Kun Qin via groups.io

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=BL1PR21MB3160D99BE89B67E601F184C2E9B82@BL1PR21MB3160.namprd21.prod.outlook.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