public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, broonie@kernel.org,
	catalin.marinas@arm.com, james.morse@arm.com,
	kaleshsingh@google.com, madvenka@linux.microsoft.com,
	maz@kernel.org, tabba@google.com
Subject: Re: [PATCH v2 6/8] arm64: stacktrace: remove stack type from fp translator
Date: Mon, 8 Aug 2022 13:30:55 +0100	[thread overview]
Message-ID: <YvEB/1JnJiCnVNo/@FVFF77S0Q05N> (raw)
In-Reply-To: <YvD8ymByprmUVSOY@FVFF77S0Q05N>

On Mon, Aug 08, 2022 at 01:08:42PM +0100, Mark Rutland wrote:
> On Mon, Aug 08, 2022 at 12:55:35PM +0100, Will Deacon wrote:
> > On Fri, Aug 05, 2022 at 01:45:20PM +0100, Mark Rutland wrote:
> 
> > >  /*
> > >   * kvm_nvhe_stack_kern_va - Convert KVM nVHE HYP stack addresses to a kernel VAs
> > >   *
> > > @@ -34,27 +62,31 @@
> > >   * Returns true on success and updates @addr to its corresponding kernel VA;
> > >   * otherwise returns false.
> > >   */
> > > -static bool kvm_nvhe_stack_kern_va(unsigned long *addr,
> > > -				   enum stack_type type)
> > > +static bool kvm_nvhe_stack_kern_va(unsigned long *addr)
> > >  {
> > >  	struct kvm_nvhe_stacktrace_info *stacktrace_info;
> > >  	unsigned long hyp_base, kern_base, hyp_offset;
> > > +	struct stack_info stack;
> > >  
> > >  	stacktrace_info = this_cpu_ptr_nvhe_sym(kvm_stacktrace_info);
> > >  
> > > -	switch (type) {
> > > -	case STACK_TYPE_HYP:
> > > +	stack = stackinfo_get_hyp();
> > > +	if (stackinfo_on_stack(&stack, *addr, 1)) {
> > >  		kern_base = (unsigned long)*this_cpu_ptr(&kvm_arm_hyp_stack_page);
> > >  		hyp_base = (unsigned long)stacktrace_info->stack_base;
> > > -		break;
> > > -	case STACK_TYPE_OVERFLOW:
> > > +		goto found;
> > > +	}
> > > +
> > > +	stack = stackinfo_get_overflow();
> > > +	if (stackinfo_on_stack(&stack, *addr, 1)) {
> > 
> > Why is '1' the appropriate size for these two checks, given that addr points
> > at an unsigned long?
> 
> That's a fair point.
> 
> My original rationale was that this was equivalent to the existing bheaviour,
> since the range has arleady been checked, but I agree it's not nice, and won't
> be right later in the series.
> 
> I'll adjust this to take an explicit size argument; the existing caller can
> pass in sizeof(unsigned long), and it can be reused for other sized objects in
> future.

FWIW, I've locally refactored this to take a size, and wrapped it with:

static bool kvm_nvhe_stack_kern_record_va(unsigned long *addr)
{
        return kvm_nvhe_stack_kern_va(addr, 16);
}

... since the frame record is actually two 8-byte values, and that matches what
unwind_next_frame_record() checks.

Thanks,
Mark.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-08-08 12:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 12:45 [PATCH v2 0/8] arm64: stacktrace: cleanups and improvements Mark Rutland
2022-08-05 12:45 ` [PATCH v2 1/8] arm64: stacktrace: simplify unwind_next_common() Mark Rutland
2022-08-05 12:45 ` [PATCH v2 2/8] arm64: stacktrace: rename unwind_next_common() -> unwind_next_frame_record() Mark Rutland
2022-08-08 11:38   ` Will Deacon
2022-08-08 11:46     ` Mark Rutland
2022-08-05 12:45 ` [PATCH v2 3/8] arm64: stacktrace: move SDEI stack helpers to stacktrace code Mark Rutland
2022-08-05 12:45 ` [PATCH v2 4/8] arm64: stacktrace: add stackinfo_on_stack() helper Mark Rutland
2022-08-05 12:45 ` [PATCH v2 5/8] arm64: stacktrace: rework stack boundary discovery Mark Rutland
2022-08-05 12:45 ` [PATCH v2 6/8] arm64: stacktrace: remove stack type from fp translator Mark Rutland
2022-08-08 11:55   ` Will Deacon
2022-08-08 12:08     ` Mark Rutland
2022-08-08 12:30       ` Mark Rutland [this message]
2022-08-08 11:56   ` Mark Brown
2022-08-05 12:45 ` [PATCH v2 7/8] arm64: stacktrace: track all stack boundaries explicitly Mark Rutland
2022-08-08 12:04   ` Mark Brown
2022-08-05 12:45 ` [PATCH v2 8/8] arm64: stacktrace: track hyp stacks in unwinder's address space Mark Rutland
2022-08-08 12:09   ` Mark Brown
2022-08-06  1:11 ` [PATCH v2 0/8] arm64: stacktrace: cleanups and improvements Madhavan T. Venkataraman
2022-08-08 11:59 ` Will Deacon
2022-08-08 12:11   ` Mark Rutland
2022-08-08 12:28     ` Will Deacon
2022-08-08 12:33       ` Mark Rutland
2022-08-08 12:38     ` Mark Brown

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=YvEB/1JnJiCnVNo/@FVFF77S0Q05N \
    --to=mark.rutland@arm.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=madvenka@linux.microsoft.com \
    --cc=maz@kernel.org \
    --cc=tabba@google.com \
    --cc=will@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