All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86/pv: Rework TRY_LOAD_SEG() to use asm goto()
Date: Mon, 21 Jul 2025 12:34:38 +0200	[thread overview]
Message-ID: <c79ecb552360253a46b7993d5909a92f@bugseng.com> (raw)
In-Reply-To: <ce45f10e-f8cc-4f34-a148-8cc69df16f8e@suse.com>

On 2025-07-21 11:25, Jan Beulich wrote:
> On 21.07.2025 10:16, Nicola Vetrini wrote:
>> On 2025-07-21 08:41, Jan Beulich wrote:
>>> On 18.07.2025 22:25, Andrew Cooper wrote:
>>>> This moves the exception path to being out-of-line within the
>>>> function, rather
>>>> than in the .fixup section, which improves backtraces.
>>>> 
>>>> Because the macro is used multiple times, the fault label needs
>>>> declaring as
>>>> local.
>>>> 
>>>> No functional change.
>>>> 
>>>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>>>> ---
>>>> CC: Jan Beulich <JBeulich@suse.com>
>>>> CC: Roger Pau Monné <roger.pau@citrix.com>
>>>> 
>>>> Slightly RFC.  I haven't checked if Eclair will be happy with
>>>> __label__ yet.
>>> 
>>> Even if it is, I guess you'd need to update the list of extensions we
>>> use (docs/misra/C-language-toolchain.rst)?
>> 
>> Only for using the __label__ token in
>> automation/eclair_analysis/ECLAIR/toolchain.ecl. The extension itself 
>> is
>> already documented in 5590c7e6590d ("eclair: allow and document use of
>> GCC extension for label addresses")
> 
> Except that it's not the address taking that is the point in question 
> here.
> We have meanwhile gained a number of asm-goto (and for the uses there 
> I'm
> not even sure they count as "address taking"). It's really the 
> __label__
> extended keyword (and the thus possible declaration of a 
> scope-restricted
> label) that my remark was about. But yes, toolchain.ecl looks to need a
> change, too.
> 

You're right, it needs also section 6.2 "Locally Declared Labels". Both 
easy to add if needed.

-- 
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253


      reply	other threads:[~2025-07-21 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18 20:25 [PATCH] x86/pv: Rework TRY_LOAD_SEG() to use asm goto() Andrew Cooper
2025-07-21  6:41 ` Jan Beulich
2025-07-21  8:16   ` Nicola Vetrini
2025-07-21  9:25     ` Jan Beulich
2025-07-21 10:34       ` Nicola Vetrini [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=c79ecb552360253a46b7993d5909a92f@bugseng.com \
    --to=nicola.vetrini@bugseng.com \
    --cc=andrew.cooper3@citrix.com \
    --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.