From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Cc: 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>
Subject: Re: [PATCH v2 0/3] xen: remove some checks for always present Xen features
Date: Fri, 30 Jul 2021 09:10:25 -0400 [thread overview]
Message-ID: <9025ef6a-6be7-ee63-b528-735f5a5e6d5e@oracle.com> (raw)
In-Reply-To: <20210730071804.4302-1-jgross@suse.com>
On 7/30/21 3:18 AM, Juergen Gross wrote:
> Some features of Xen can be assumed to be always present, so add a
> central check to verify this being true and remove the other checks.
>
> Juergen Gross (3):
> xen: check required Xen features
> xen: assume XENFEAT_mmu_pt_update_preserve_ad being set for pv guests
> xen: assume XENFEAT_gnttab_map_avail_bits being set for pv guests
>
> arch/x86/xen/enlighten_pv.c | 12 ++----------
> arch/x86/xen/mmu_pv.c | 4 ++--
> drivers/xen/features.c | 18 ++++++++++++++++++
> drivers/xen/gntdev.c | 36 ++----------------------------------
> 4 files changed, 24 insertions(+), 46 deletions(-)
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
prev parent reply other threads:[~2021-07-30 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 7:18 [PATCH v2 0/3] xen: remove some checks for always present Xen features Juergen Gross
2021-07-30 7:18 ` [PATCH v2 1/3] xen: check required " Juergen Gross
2021-07-30 7:18 ` [PATCH v2 2/3] xen: assume XENFEAT_mmu_pt_update_preserve_ad being set for pv guests Juergen Gross
2021-07-30 7:18 ` [PATCH v2 3/3] xen: assume XENFEAT_gnttab_map_avail_bits " Juergen Gross
2021-07-30 13:10 ` Boris Ostrovsky [this message]
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=9025ef6a-6be7-ee63-b528-735f5a5e6d5e@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.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;
as well as URLs for NNTP newsgroup(s).