From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Wei Liu" <wl@xen.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Ian Jackson" <Ian.Jackson@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
"Daniel De Graaf" <dgdegra@tycho.nsa.gov>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH 1/2] xen: Drop XEN_DOMCTL_suppress_spurious_page_faults
Date: Tue, 27 Aug 2019 17:39:49 +0200 [thread overview]
Message-ID: <bfcac2fc-72e2-b3c4-64d1-33a16230b61f@suse.com> (raw)
In-Reply-To: <20190813105352.32412-2-andrew.cooper3@citrix.com>
On 13.08.2019 12:53, Andrew Cooper wrote:
> This functionality is obsolete. It was introduced by c/s 39407bed9c0 into
> Xend, but never exposed in libxl.
This is good enough a reason I think (hope), while ...
> While not explicitly limited to PV guests, this is PV-only by virtue of its
> position in the pagefault handler.
>
> Looking though the XenServer templates, this was used to work around bugs in
> the 32bit RHEL/CentOS 4.{5..7} kernels (fixed in 4.8). RHEL 4 as a major
> version when out if support in 2017.
... I wouldn't accept this as justification, since people are
free to use out-of-support software for as long as they wish.
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Hypervisor parts
Reviewed-by: Jan Beulich <jbeulich@suse.com>
with one further suggestion:
> --- a/xen/arch/x86/traps.c
> +++ b/xen/arch/x86/traps.c
> @@ -1452,20 +1452,6 @@ void do_page_fault(struct cpu_user_regs *regs)
> error_code, _p(addr));
> }
>
> - if ( unlikely(current->domain->arch.suppress_spurious_page_faults) )
> - {
> - pf_type = spurious_page_fault(addr, regs);
> - if ( (pf_type == smep_fault) || (pf_type == smap_fault))
> - {
> - printk(XENLOG_G_ERR "%pv fatal SM%cP violation\n",
> - current, (pf_type == smep_fault) ? 'E' : 'A');
> -
> - domain_crash(current->domain);
> - }
> - if ( pf_type != real_fault )
> - return;
> - }
You may want to consider reducing pf_type's scope at the same
time.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-27 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 10:53 [Xen-devel] [PATCH 0/2] xen: Drop obsolete DOMCTLs Andrew Cooper
2019-08-13 10:53 ` [Xen-devel] [PATCH 1/2] xen: Drop XEN_DOMCTL_suppress_spurious_page_faults Andrew Cooper
2019-08-13 18:58 ` Marek Marczykowski-Górecki
2019-08-27 15:39 ` Jan Beulich [this message]
2019-08-28 14:30 ` Andrew Cooper
2019-08-13 10:53 ` [Xen-devel] [PATCH 2/2] xen: Drop XEN_DOMCTL_{get, set}_machine_address_size Andrew Cooper
2019-08-13 18:59 ` Marek Marczykowski-Górecki
2019-08-14 12:15 ` Christian Lindig
2019-08-27 15:47 ` Jan Beulich
2019-08-14 12:16 ` [Xen-devel] [PATCH 0/2] xen: Drop obsolete DOMCTLs Wei Liu
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=bfcac2fc-72e2-b3c4-64d1-33a16230b61f@suse.com \
--to=jbeulich@suse.com \
--cc=Ian.Jackson@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.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).