From: Sean Christopherson <seanjc@google.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Anish Moorthy <amoorthy@google.com>,
Shuah Khan <shuah@kernel.org>,
Nicolas Saenz Julienne <nsaenz@amazon.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [PATCH] KVM: selftests: Drop stale exact flags check in private_mem_kvm_exits_test
Date: Thu, 12 Nov 2026 09:22:38 -0800 [thread overview]
Message-ID: <avX13o0qRkidIwWo@google.com> (raw)
In-Reply-To: <20261112144220.30801-1-dwmw2@infradead.org>
On Thu, Nov 12, 2026, David Woodhouse wrote:
> From: David Woodhouse <dwmw@amazon.co.uk>
>
> Commit 7d0afe669374 ("KVM: selftests: Take into account mixed memory
> fault flags") relaxed the memory_fault.flags checks so that they only
> test for KVM_MEMORY_EXIT_FLAG_PRIVATE, since KVM may report the access
> type alongside it. In test_private_access_memslot_deleted() it added
> the relaxed check but left the exact match above it, and with the
> READ flag now reported the test fails for me there:
Ah, this is against kvm/kvm-memprot-v4.
Paolo, what are your plans with that branch? Sashiko had valid complaints, e.g.
against patch 1[*], so I assume the branch won't be merged as-is.
[*] https://lore.kernel.org/all/sashiko-outbox-193903@kernel.org
next prev parent reply other threads:[~2026-11-12 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 14:42 [PATCH] KVM: selftests: Drop stale exact flags check in private_mem_kvm_exits_test David Woodhouse
2026-11-12 17:22 ` Sean Christopherson [this message]
2026-11-12 17:42 ` David Woodhouse
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=avX13o0qRkidIwWo@google.com \
--to=seanjc@google.com \
--cc=amoorthy@google.com \
--cc=dwmw2@infradead.org \
--cc=dwmw@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=nsaenz@amazon.com \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.