From: Youngmin Nam <youngmin.nam@samsung.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: lexandru.elisei@arm.com, andreyknvl@gmail.com,
anshuman.khandual@arm.com, ardb@kernel.org, broonie@kernel.org,
catalin.marinas@arm.com, d7271.choe@samsung.com,
dvyukov@google.com, hy50.seo@samsung.com,
kasan-dev@googlegroups.com, linux-arm-kernel@lists.infradead.org,
maz@kernel.org, will@kernel.org, youngmin.nam@samsung.com
Subject: Re: [PATCH] arm64: set __exception_irq_entry with __irq_entry as a default
Date: Fri, 26 May 2023 08:20:36 +0900 [thread overview]
Message-ID: <ZG/tRDjl4uR7C0dD@perf> (raw)
In-Reply-To: <ZF5gmBz4NbDseDHp@FVFF77S0Q05N>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
On Fri, May 12, 2023 at 04:51:52PM +0100, Mark Rutland wrote:
> Hi,
>
> On Fri, May 12, 2023 at 08:46:56AM +0900, Youngmin Nam wrote:
> > On Wed, Apr 26, 2023 at 02:06:25PM +0900, Youngmin Nam wrote:
> > > On Tue, Apr 25, 2023 at 02:39:51PM +0100, Mark Rutland wrote:
> > > > On Tue, Apr 25, 2023 at 11:31:31AM +0900, Youngmin Nam wrote:
> > > > > On Mon, Apr 24, 2023 at 02:08:14PM +0100, Mark Rutland wrote:
> > > > > > With that in mind, I think what we should do is cut this at the instant we
> > > > > > enter the exception; for the trace below that would be el1h_64_irq. I've added
> > > > > > some line spacing there to make it stand out.
>
> > > > I'd meant something like the below, marking the assembly (as x86 does) rather
> > > > than the C code. I'll try to sort that out and send a proper patch series after
> > > > -rc1.
> > > >
> > > > Thanks,
> > > > Mark.
> >
> > Hi Mark.
> > This is gentle remind for you.
> > Can I know that you've sent the patch ?
> > Actually I'm looking forward to seeing your patch. :)
>
> Sorry; I haven't yet sent this out as I'm still looking into how this interacts
> with ftrace.
>
> I'll try to flesh out the commit message and get this out next week. You will
> be Cc'd when I send it out.
>
> Thanks,
> Mark.
>
Hi Mark.
Sorry to rush you. Would you share your patch for us ? We're still waiting
your patch. :)
Thanks.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-25 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230424003252epcas2p29758e056b4766e53c252b5927a0cb406@epcas2p2.samsung.com>
2023-04-24 1:04 ` [PATCH] arm64: set __exception_irq_entry with __irq_entry as a default Youngmin Nam
2023-04-24 6:48 ` Dmitry Vyukov
2023-04-24 11:01 ` Mark Rutland
2023-04-24 12:09 ` Dmitry Vyukov
2023-04-24 13:08 ` Mark Rutland
2023-04-25 2:31 ` Youngmin Nam
2023-04-25 13:39 ` Mark Rutland
2023-04-26 5:06 ` Youngmin Nam
[not found] ` <ZF1+cLp7Io7L25yG@perf>
[not found] ` <ZF5gmBz4NbDseDHp@FVFF77S0Q05N>
2023-05-25 23:20 ` Youngmin Nam [this message]
2023-06-08 9:03 ` Mark Rutland
2023-06-08 18:17 ` Catalin Marinas
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=ZG/tRDjl4uR7C0dD@perf \
--to=youngmin.nam@samsung.com \
--cc=andreyknvl@gmail.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=d7271.choe@samsung.com \
--cc=dvyukov@google.com \
--cc=hy50.seo@samsung.com \
--cc=kasan-dev@googlegroups.com \
--cc=lexandru.elisei@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).