From: Lai Jiangshan <jiangshanlai@gmail.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Lai Jiangshan <jiangshan.ljs@antgroup.com>,
Joerg Roedel <jroedel@suse.de>, Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/sev: Add ENCODE_FRAME_POINTER after stack changed for #VC
Date: Wed, 27 Apr 2022 16:26:59 +0800 [thread overview]
Message-ID: <CAJhGHyBbN82UTEqFy1_=bPo+8a13S24jUzwKu5o5jJu3jbkETA@mail.gmail.com> (raw)
In-Reply-To: <CAJhGHyAjXgqxxH+myLt0nMcSLQWWLrcOb8WevyQNf-Oajip7-A@mail.gmail.com>
On Tue, Apr 12, 2022 at 8:24 PM Lai Jiangshan <jiangshanlai@gmail.com> wrote:
>
> On Sat, Mar 19, 2022 at 1:03 AM Josh Poimboeuf <jpoimboe@redhat.com> wrote:
>
> > Ok, maybe Joerg can test it. It looks obviously right to me though.
>
> It looks also obviously right to me.
>
> Hello, Joerg
>
> Any feedback?
>
> > Since it fixes a real frame pointer unwinding bug, it probably needs:
> >
> > Fixes: a13644f3a53d ("x86/entry/64: Add entry code for #VC handler")
> >
> > Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
>
> Hello, Borislav
>
> Can you have a look at the patch, please?
>
> Thanks
> Lai
Hello
Ping.
Thanks
Lai
next prev parent reply other threads:[~2022-04-27 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 4:16 [PATCH] x86/sev: Add ENCODE_FRAME_POINTER after stack changed for #VC Lai Jiangshan
2022-03-17 22:19 ` Josh Poimboeuf
2022-03-18 1:14 ` Lai Jiangshan
2022-03-18 17:03 ` Josh Poimboeuf
2022-04-12 12:24 ` Lai Jiangshan
2022-04-27 8:26 ` Lai Jiangshan [this message]
2022-05-13 9:04 ` Lai Jiangshan
2022-05-18 18:44 ` [tip: x86/sev] x86/sev: Annotate stack change in the #VC handler tip-bot2 for Lai Jiangshan
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='CAJhGHyBbN82UTEqFy1_=bPo+8a13S24jUzwKu5o5jJu3jbkETA@mail.gmail.com' \
--to=jiangshanlai@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jiangshan.ljs@antgroup.com \
--cc=jpoimboe@redhat.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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).