mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 0/7] Incorporate DRAM address in EDAC messages
Date: Mon, 28 Sep 2026 11:12:51 -0400	[thread overview]
Message-ID: <20260928151251.GC2289128@yaz-khff2.amd.com> (raw)
In-Reply-To: <20260928053040.GCarn7gHIDY6qPkZNi@fat_crate.local>

On Sun, Sep 27, 2026 at 10:30:40PM -0700, Borislav Petkov wrote:
> On Tue, Sep 22, 2026 at 03:23:10PM -0500, Yazen Ghannam wrote:
> > This revision addresses a couple comments from Boris. Also, the couple
> > of patches originally by Avadhut have gone through a few revisions. So I
> > updated the attributions.
> 
> One Sashiko question here:
> 
> https://sashiko.dev/#/patchset/20260922202318.4079080-1-yazen.ghannam%40amd.com
> 

Looks like a false positive.

The question is on a struct that was added in patch 3. And that patch
was reviewed as good.

Also, pahole shows that the nested struct is packed. Sashiko said is
isn't.

Nested struct => struct atl_umc_addr

 $ pahole build/drivers/ras/amd/atl/prm.o
struct atl_umc_addr {
        u64                        addr;                 /*     0     8 */
        u8                         socket_id;            /*     8     1 */
        u64                        ipid;                 /*     9     8 */

        /* size: 17, cachelines: 1, members: 3 */
        /* last cacheline: 17 bytes */
} __attribute__((__packed__));
struct param_buf {
        struct atl_umc_addr        addr;                 /*     0    17 */
        void *                     out_buf;              /*    17     8 */

        /* size: 25, cachelines: 1, members: 2 */
        /* last cacheline: 25 bytes */
} __attribute__((__packed__));

Thanks,
Yazen

      reply	other threads:[~2026-09-28 15:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 20:23 Yazen Ghannam
2026-09-22 20:23 ` [PATCH v10 1/7] RAS/AMD/ATL: Make PRM address translation support builtin Yazen Ghannam
2026-09-22 20:23 ` [PATCH v10 2/7] RAS/AMD/ATL: Refactor PRM address translation into a common helper Yazen Ghannam
2026-09-22 20:23 ` [PATCH v10 3/7] RAS/AMD/ATL: Add unified UMC address translation interface Yazen Ghannam
2026-09-22 20:23 ` [PATCH v10 4/7] RAS/AMD, EDAC/amd64: Use unified interface for SPA translation Yazen Ghannam
2026-09-22 20:23 ` [PATCH v10 5/7] RAS/AMD/ATL: Remove the standalone SPA translation interface Yazen Ghannam
2026-09-22 20:23 ` [PATCH v10 6/7] RAS/AMD/ATL: Add DRAM address translation via PRM Yazen Ghannam
2026-09-22 20:23 ` [PATCH v10 7/7] EDAC/amd64: Include DRAM address in output Yazen Ghannam
2026-09-28  5:30 ` [PATCH v10 0/7] Incorporate DRAM address in EDAC messages Borislav Petkov
2026-09-28 15:12   ` Yazen Ghannam [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-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=20260928151251.GC2289128@yaz-khff2.amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®