All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>
To: "Jan Beulich" <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 2/2] tools/hvmloader: Replace LAPIC_ID() with cpu_to_apicid[]
Date: Tue, 04 Feb 2025 17:25:28 +0000	[thread overview]
Message-ID: <D7JU528VWICI.3FVRRY1LXY363@cloud.com> (raw)
In-Reply-To: <c179a661-d705-41da-988a-ff361ceaa1f9@suse.com>

On Tue Feb 4, 2025 at 3:46 PM GMT, Jan Beulich wrote:
> On 04.02.2025 16:25, Alejandro Vallejo wrote:
> > On Tue Feb 4, 2025 at 3:07 PM GMT, Jan Beulich wrote:
> >> On 04.02.2025 15:45, Alejandro Vallejo wrote:
> >>> --- a/tools/firmware/hvmloader/config.h
> >>> +++ b/tools/firmware/hvmloader/config.h
> >>> @@ -48,8 +48,9 @@ extern uint8_t ioapic_version;
> >>>  
> >>>  #define IOAPIC_ID           0x01
> >>>  
> >>> +extern uint32_t *cpu_to_apicid;
> >>
> >> Strictly speaking this ought to be part of the earlier patch. If hvmloader
> >> was Misra-checked, this would be a (transient) violation.
> > 
> > Hmmm. I don't see it. The previous patch is fully contained in smp.c and this
> > extern isn't required until now. Does MISRA have mandates on non-static symbols
> > not present in headers?
>
> Every non-static definition is expected to have exactly one earlier
> declaration.
>
> Jan

I had no idea. Fair enough then, I'll adjust...

Cheers,
Alejandro


      reply	other threads:[~2025-02-04 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 14:45 [PATCH v2 0/2] tools/hvmloader: Decouple APIC IDs from vCPU IDs Alejandro Vallejo
2025-02-04 14:45 ` [PATCH v2 1/2] tools/hvmloader: Retrieve APIC IDs from the APs themselves Alejandro Vallejo
2025-02-04 14:45 ` [PATCH v2 2/2] tools/hvmloader: Replace LAPIC_ID() with cpu_to_apicid[] Alejandro Vallejo
2025-02-04 15:07   ` Jan Beulich
2025-02-04 15:25     ` Alejandro Vallejo
2025-02-04 15:46       ` Jan Beulich
2025-02-04 17:25         ` Alejandro Vallejo [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=D7JU528VWICI.3FVRRY1LXY363@cloud.com \
    --to=alejandro.vallejo@cloud.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.