From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>, Wei Liu <wl@xen.org>,
Andy Lutomirski <luto@kernel.org>,
Manuel Bouyer <bouyer@antioche.eu.org>
Subject: Re: [PATCH v2] x86/pv: Inject #UD for missing SYSCALL callbacks
Date: Wed, 14 Oct 2020 16:17:05 +0100 [thread overview]
Message-ID: <416f9d8d-532a-6b72-1e06-a325f0edaaab@citrix.com> (raw)
In-Reply-To: <20201014141620.GS19254@Air-de-Roger>
On 14/10/2020 15:16, Roger Pau Monné wrote:
>> This change does constitute a change in the PV ABI, for corner cases of a PV
>> guest kernel registering neither callback, or not registering the 32bit
>> callback when running on AMD/Hygon hardware.
> Is there any place suitable to document this behavior?
In the short term, my XTF test which will eventually get into CI.
Longer term, my theoretical future where I've described some of this
stuff in docs/guest-guide/
~Andrew
next prev parent reply other threads:[~2020-10-14 15:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 10:18 [PATCH 0/3] x86/pv: Multiple fixes to SYSCALL/SYSENTER handling (XSA-339 followup) Andrew Cooper
2020-09-23 10:18 ` [PATCH 1/3] x86/pv: Don't deliver #GP for a SYSENTER with NT set Andrew Cooper
2020-09-24 13:55 ` Jan Beulich
2020-09-23 10:18 ` [PATCH 2/3] x86/pv: Don't clobber NT on return-to-guest Andrew Cooper
2020-09-24 13:57 ` Jan Beulich
2020-09-23 10:18 ` [PATCH 3/3] x86/pv: Inject #UD for missing SYSCALL callbacks Andrew Cooper
2020-09-24 14:56 ` Jan Beulich
2020-09-28 13:05 ` Andrew Cooper
2020-09-28 15:35 ` Jan Beulich
2020-10-09 11:53 ` [PATCH v2] " Andrew Cooper
2020-10-09 12:40 ` Manuel Bouyer
2020-10-09 12:50 ` Andrew Cooper
2020-10-14 14:16 ` Roger Pau Monné
2020-10-14 14:20 ` Manuel Bouyer
2020-10-14 14:26 ` Andrew Cooper
2020-10-14 15:17 ` Andrew Cooper [this message]
2020-10-14 16:28 ` Roger Pau Monné
2020-10-14 17:41 ` Andrew Cooper
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=416f9d8d-532a-6b72-1e06-a325f0edaaab@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=bouyer@antioche.eu.org \
--cc=luto@kernel.org \
--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).