From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
kvm@vger.kernel.org, Maxim Levitsky <mlevitsk@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, x86@kernel.org,
linux-kselftest@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v2 0/2] KVM: x86: read the PML log in the same order it was written
Date: Thu, 9 Jan 2025 11:47:25 -0800 [thread overview]
Message-ID: <173645201741.890420.7594833670950629627.b4-ty@google.com> (raw)
In-Reply-To: <20241219221034.903927-1-mlevitsk@redhat.com>
On Thu, 19 Dec 2024 17:10:32 -0500, Maxim Levitsky wrote:
> Reverse the order in which
> the PML log is read to align more closely to the hardware. It should
> not affect regular users of the dirty logging but it fixes a unit test
> specific assumption in the dirty_log_test dirty-ring mode.
>
> Best regards,
> Maxim Levitsky
>
> [...]
Applied to kvm-x86 vmx, thanks!
[1/2] KVM: VMX: refactor PML terminology
https://github.com/kvm-x86/linux/commit/ae81ce936ff9
[2/2] KVM: VMX: read the PML log in the same order as it was written
https://github.com/kvm-x86/linux/commit/37c3ddfe5238
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2025-01-09 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 22:10 Maxim Levitsky
2024-12-19 22:10 ` [PATCH v2 1/2] KVM: VMX: refactor PML terminology Maxim Levitsky
2024-12-19 22:10 ` [PATCH v2 2/2] KVM: VMX: read the PML log in the same order as it was written Maxim Levitsky
2025-01-09 19:47 ` Sean Christopherson [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=173645201741.890420.7594833670950629627.b4-ty@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®