From: Sean Christopherson <seanjc@google.com>
To: Mathias Krause <minipli@grsecurity.net>
Cc: kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v3 3/4] x86/access: Forced emulation support
Date: Mon, 3 Apr 2023 17:08:21 -0700 [thread overview]
Message-ID: <ZCtqdYRIeaCZOwT3@google.com> (raw)
In-Reply-To: <4f77d3a6-ed17-051e-5aa3-17fc3ab6dc7f@grsecurity.net>
On Mon, Apr 03, 2023, Mathias Krause wrote:
> On 03.04.23 21:06, Sean Christopherson wrote:
> > Keeping KVM-Unit-Tests and KVM synchronized on the correct FEP value would be a
> > pain, but disconnects between KVM and KUT are nothing new.
>
> Nah, that would be an ABI break, IMO a no-go. What I was suggesting was
> pretty much the patch: change selective users in KUT to make them
> objdump-friendly. The FEP as-is is ABI, IMO
I would be amazed if anything other that KVM's own tests utilizes the feature.
IMO, it really shouldn't be considered ABI.
Paolo?
next prev parent reply other threads:[~2023-04-04 0:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 10:56 [kvm-unit-tests PATCH v3 0/4] Tests for CR0.WP=0/1 r/o write access Mathias Krause
2023-04-03 10:56 ` [kvm-unit-tests PATCH v3 1/4] x86: Use existing CR0.WP / CR4.SMEP bit definitions Mathias Krause
2023-04-03 10:56 ` [kvm-unit-tests PATCH v3 2/4] x86/access: CR0.WP toggling write to r/o data test Mathias Krause
2023-04-03 10:56 ` [kvm-unit-tests PATCH v3 3/4] x86/access: Forced emulation support Mathias Krause
2023-04-03 11:28 ` Mathias Krause
2023-04-03 19:06 ` Sean Christopherson
2023-04-03 20:06 ` Mathias Krause
2023-04-04 0:08 ` Sean Christopherson [this message]
2023-04-04 0:04 ` Sean Christopherson
2023-04-04 7:27 ` Mathias Krause
2023-04-04 16:36 ` Sean Christopherson
2023-04-05 8:01 ` Mathias Krause
2023-04-03 10:56 ` [kvm-unit-tests PATCH v3 4/4] x86/access: Try emulation for CR0.WP test as well Mathias Krause
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=ZCtqdYRIeaCZOwT3@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=minipli@grsecurity.net \
/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