From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: peterz@infradead.org, Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, Deep Shah <sdeep@vmware.com>,
"VMware, Inc." <pv-drivers@vmware.com>
Subject: [PATCH v2 0/2] x86/xen: simplify irq pvops
Date: Wed, 22 Sep 2021 12:31:00 +0200 [thread overview]
Message-ID: <20210922103102.3589-1-jgross@suse.com> (raw)
The pvops function for Xen PV guests handling the interrupt flag are
much more complex than needed.
With the supported Xen hypervisor versions they can be simplified a
lot, especially by removing the need for disabling preemption.
Juergen Gross (2):
x86/xen: remove xen_have_vcpu_info_placement flag
x86/xen: switch initial pvops IRQ functions to dummy ones
arch/x86/include/asm/paravirt_types.h | 2 +
arch/x86/kernel/paravirt.c | 13 ++-
arch/x86/xen/enlighten.c | 116 ++++++--------------------
arch/x86/xen/enlighten_hvm.c | 6 +-
arch/x86/xen/enlighten_pv.c | 28 ++-----
arch/x86/xen/irq.c | 61 +-------------
arch/x86/xen/smp.c | 24 ------
arch/x86/xen/xen-ops.h | 4 +-
8 files changed, 53 insertions(+), 201 deletions(-)
--
2.26.2
next reply other threads:[~2021-09-22 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 10:31 Juergen Gross [this message]
2021-09-22 10:31 ` [PATCH v2 1/2] x86/xen: remove xen_have_vcpu_info_placement flag Juergen Gross
2021-09-22 21:43 ` Boris Ostrovsky
2021-09-23 4:44 ` Juergen Gross
2021-09-23 14:09 ` Boris Ostrovsky
2021-09-22 10:31 ` [PATCH v2 2/2] x86/xen: switch initial pvops IRQ functions to dummy ones Juergen Gross
2021-09-22 21:49 ` Boris Ostrovsky
2021-09-23 4:45 ` Juergen Gross
2021-09-22 12:46 ` [PATCH v2 0/2] x86/xen: simplify irq pvops 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=20210922103102.3589-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pv-drivers@vmware.com \
--cc=sdeep@vmware.com \
--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;
as well as URLs for NNTP newsgroup(s).