From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org,
virtualization@lists.linux-foundation.org,
linux-trace-kernel@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
xen-devel@lists.xenproject.org, Ajay Kaher <akaher@vmware.com>,
Alexey Makhalov <amakhalov@vmware.com>,
VMware PV-Drivers Reviewers <pv-drivers@vmware.com>,
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>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: [PATCH 0/3] xen: cleanup and fix lazy mode handling
Date: Wed, 13 Sep 2023 13:38:25 +0200 [thread overview]
Message-ID: <20230913113828.18421-1-jgross@suse.com> (raw)
This small series is cleaning up Xen lazy mode handling by removing
unused stuff and moving purely Xen-specific code away from general
kernel code.
The last patch is fixing a regression which was introduced in the
6.6 merge window.
Juergen Gross (3):
arm/xen: remove lazy mode related definitions
x86/xen: move paravirt lazy code
x86/xen: allow nesting of same lazy mode
arch/x86/include/asm/paravirt_types.h | 15 ------
arch/x86/include/asm/xen/hypervisor.h | 37 +++++++++++++++
arch/x86/kernel/paravirt.c | 67 ---------------------------
arch/x86/xen/enlighten_pv.c | 40 +++++++++++++---
arch/x86/xen/mmu_pv.c | 55 ++++++++++++++--------
arch/x86/xen/multicalls.h | 4 +-
include/trace/events/xen.h | 12 ++---
include/xen/arm/hypervisor.h | 12 -----
8 files changed, 114 insertions(+), 128 deletions(-)
--
2.35.3
next reply other threads:[~2023-09-13 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 11:38 Juergen Gross [this message]
2023-09-13 11:38 ` [PATCH 2/3] x86/xen: move paravirt lazy code Juergen Gross
2023-09-13 13:26 ` Steven Rostedt
2023-09-13 13:36 ` Juergen Gross
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=20230913113828.18421-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=pv-drivers@vmware.com \
--cc=rostedt@goodmis.org \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--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