From: John Allen <john.allen@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: rafael@kernel.org, lenb@kernel.org, yazen.ghannam@amd.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org
Subject: Re: [PATCH v2 2/2] RAS/AMD/ATL: Translate normalized to system physical addresses using PRM
Date: Mon, 1 Jul 2024 11:43:35 -0500 [thread overview]
Message-ID: <ZoLct9pSnqXm4OFd@AUS-L1-JOHALLEN.amd.com> (raw)
In-Reply-To: <20240701163424.GHZoLakCmNflWa_Lzm@fat_crate.local>
On Mon, Jul 01, 2024 at 06:35:05PM +0200, Borislav Petkov wrote:
> On Mon, Jul 01, 2024 at 11:23:36AM -0500, John Allen wrote:
> > This is the param buffer struct used for norm -> X tranlations. I can
> > shorten and clarify this along with the others you pointed out. Maybe
> > "param_buffer_norm" instead and a comment explaining the purpose?
>
> What's wrong with
>
> struct param_buffer
>
> simply?
>
> It is obvious from the code that it is used in the normalized -> physical
> address translation.
This is because the spec defines different param buffer structures for
different types of translation. We can call this just param_buffer for
now, but would need to be renamed if/when we add use cases for the other
translation handlers. My preference would be to sort of future-proof
the name now, but I don't have an issue calling it param_buffer now and
changing it later if that's what you'd prefer.
> Btw, pls do me a favor and trim your replies like I just did.
Sure, sorry about that.
Thanks,
John
next prev parent reply other threads:[~2024-07-01 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 17:47 [PATCH v2 0/2] PRM handler direct call interface John Allen
2024-05-06 17:47 ` [PATCH v2 1/2] ACPI: PRM: Add PRM handler direct call support John Allen
2024-06-26 19:21 ` Rafael J. Wysocki
2024-06-27 8:08 ` Borislav Petkov
2024-07-02 14:54 ` Ard Biesheuvel
2024-05-06 17:47 ` [PATCH v2 2/2] RAS/AMD/ATL: Translate normalized to system physical addresses using PRM John Allen
2024-06-28 7:45 ` Borislav Petkov
2024-07-01 16:23 ` John Allen
2024-07-01 16:35 ` Borislav Petkov
2024-07-01 16:43 ` John Allen [this message]
2024-07-01 16:59 ` Borislav Petkov
2024-07-03 20:14 ` John Allen
2024-07-03 22:46 ` Borislav Petkov
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-all 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=ZoLct9pSnqXm4OFd@AUS-L1-JOHALLEN.amd.com \
--to=john.allen@amd.com \
--cc=bp@alien8.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=yazen.ghannam@amd.com \
/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
all inboxes | Powered by JetHome®