mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julien Thierry <jthierry@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: linux-kernel@vger.kernel.org, jpoimboe@redhat.com,
	peterz@infradead.org, raphael.gault@arm.com
Subject: Re: [RFC PATCH 7/7] objtool: Make unwind_hints available for all architectures
Date: Thu, 11 Jun 2020 08:20:31 +0100	[thread overview]
Message-ID: <c4518f15-545a-3cb5-214b-29ddc068189b@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.21.2006101516310.26666@pobox.suse.cz>

Hi Miroslav,

On 6/10/20 2:20 PM, Miroslav Benes wrote:
> Hi Julien,
> 
> On Mon, 8 Jun 2020, Julien Thierry wrote:
> 
>> Unwind hints are useful to give some information about the call frame
>> or stack states in non-standard code.
>>
>> Despite unwind hints being used in arch-independent code, the
>> unwind_hint structure type itself is define in x86 kernel headers.
>>
>> This is because what an unwind hint will describe is very architecture
>> specific, both regarding the state and the affected registers.
>>
>> To get to share this concept, expose the unwind_hint structure across
>> architecutres. However, the hint types remain defined by the
>> architecture code. Objtool then needs it's arch specific code to
>> "decode" the unwind hint into a cfi_state.
> 
> I think it would be nice to split the patch. Something like.
> 
> 1. current include/linux/frame.h mixes assembly and non-assembly
> definitions, so introduce ASSEMBLY ifdef first seems like a good idea to
> me.
> 
> 2. move the relevant definitions to frame.h and add the file to
> sync-check
> 
> 3. the rest of the patch
> 
> Would it make sense?
> 

Yes, I think your approach will make it simpler to review. I wasn't sure 
how to split it but I like your suggestion, thank you for it.

I'll probably post the split patch separately if the rest of the series 
gets picked.

Cheers,

-- 
Julien Thierry


  reply	other threads:[~2020-06-11  7:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 15:27 [PATCH 0/7] Make check implementation arch agnostic Julien Thierry
2020-06-08 15:27 ` [PATCH 1/7] objtool: Group headers to check in a single list Julien Thierry
2020-06-08 15:27 ` [PATCH 2/7] objtool: Make sync-check consider the target architecture Julien Thierry
2020-06-08 15:27 ` [PATCH 3/7] objtool: Move macros describing structures to arch-dependent code Julien Thierry
2020-06-08 15:27 ` [PATCH 4/7] objtool: Abstract alternative special case handling Julien Thierry
2020-06-08 15:27 ` [PATCH 5/7] objtool: Make relocation in alternative handling arch dependent Julien Thierry
2020-06-08 15:27 ` [PATCH 6/7] objtool: Refactor switch-tables code to support other architectures Julien Thierry
2020-06-08 15:27 ` [RFC PATCH 7/7] objtool: Make unwind_hints available for all architectures Julien Thierry
2020-06-10 13:20   ` Miroslav Benes
2020-06-11  7:20     ` Julien Thierry [this message]
2020-06-10 13:20 ` [PATCH 0/7] Make check implementation arch agnostic Miroslav Benes

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=c4518f15-545a-3cb5-214b-29ddc068189b@redhat.com \
    --to=jthierry@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=peterz@infradead.org \
    --cc=raphael.gault@arm.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®