From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: 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>,
xen-devel@lists.xenproject.org,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/2] x86/xen: don't return from xen_pv_play_dead()
Date: Mon, 16 Jan 2023 15:46:39 -0500 [thread overview]
Message-ID: <4f7189ca-afd6-25cf-38a0-80b53526c2fe@oracle.com> (raw)
In-Reply-To: <d0c6363f-d5c9-a53b-5275-e5134b54f09a@suse.com>
On 1/16/23 2:49 AM, Juergen Gross wrote:
> On 25.11.22 07:32, Juergen Gross wrote:
>> All play_dead() functions but xen_pv_play_dead() don't return to the
>> caller.
>>
>> Adapt xen_pv_play_dead() to behave like the other play_dead() variants.
>>
>> Juergen Gross (2):
>> x86/xen: don't let xen_pv_play_dead() return
>> x86/xen: mark xen_pv_play_dead() as __noreturn
>>
>> arch/x86/xen/smp.h | 2 ++
>> arch/x86/xen/smp_pv.c | 17 ++++-------------
>> arch/x86/xen/xen-head.S | 7 +++++++
>> tools/objtool/check.c | 1 +
>> 4 files changed, 14 insertions(+), 13 deletions(-)
>>
>
> Ping?
>
>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
next prev parent reply other threads:[~2023-01-16 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 6:32 Juergen Gross
2022-11-25 6:32 ` [PATCH 1/2] x86/xen: don't let xen_pv_play_dead() return Juergen Gross
2023-02-12 10:03 ` [tip: objtool/core] " tip-bot2 for Juergen Gross
2022-11-25 6:32 ` [PATCH 2/2] x86/xen: mark xen_pv_play_dead() as __noreturn Juergen Gross
2023-02-12 10:03 ` [tip: objtool/core] " tip-bot2 for Juergen Gross
2023-01-16 7:49 ` [PATCH 0/2] x86/xen: don't return from xen_pv_play_dead() Juergen Gross
2023-01-16 20:46 ` Boris Ostrovsky [this message]
2023-01-16 9:12 ` Peter Zijlstra
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=4f7189ca-afd6-25cf-38a0-80b53526c2fe@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--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 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®