From: David Woodhouse <dwmw2@infradead.org>
To: Paul Durrant <paul@xen.org>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 08/15] KVM: pfncache: allow a cache to be activated with a fixed (userspace) HVA
Date: Wed, 22 Nov 2023 12:25:05 +0000 [thread overview]
Message-ID: <c7623704c17f3ea2622b700dde525522701c02c7.camel@infradead.org> (raw)
In-Reply-To: <20231122121822.1042-9-paul@xen.org>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Wed, 2023-11-22 at 12:18 +0000, Paul Durrant wrote:
> From: Paul Durrant <pdurrant@amazon.com>
>
> Some pfncache pages may actually be overlays on guest memory that have a
> fixed HVA within the VMM. It's pointless to invalidate such cached
> mappings if the overlay is moved so allow a cache to be activated directly
> with the HVA to cater for such cases. A subsequent patch will make use
> of this facility.
>
> Signed-off-by: Paul Durrant <pdurrant@amazon.com>
I like that better now. Thank you.
Reviewed-by: David Woodhouse <dwmw@amazon.co.uk>
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2023-11-22 12:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 12:18 [PATCH v9 00/15] KVM: xen: update shared_info and vcpu_info handling Paul Durrant
2023-11-22 12:18 ` [PATCH v9 01/15] KVM: pfncache: Add a map helper function Paul Durrant
2023-11-22 12:18 ` [PATCH v9 02/15] KVM: pfncache: remove unnecessary exports Paul Durrant
2023-11-22 12:18 ` [PATCH v9 03/15] KVM: xen: mark guest pages dirty with the pfncache lock held Paul Durrant
2023-11-22 12:18 ` [PATCH v9 04/15] KVM: pfncache: add a mark-dirty helper Paul Durrant
2023-11-22 12:24 ` David Woodhouse
2023-11-22 13:04 ` Paul Durrant
2023-11-22 12:18 ` [PATCH v9 05/15] KVM: pfncache: remove KVM_GUEST_USES_PFN usage Paul Durrant
2023-11-22 12:18 ` [PATCH v9 06/15] KVM: pfncache: stop open-coding offset_in_page() Paul Durrant
2023-11-22 12:18 ` [PATCH v9 07/15] KVM: pfncache: include page offset in uhva and use it consistently Paul Durrant
2023-11-22 12:18 ` [PATCH v9 08/15] KVM: pfncache: allow a cache to be activated with a fixed (userspace) HVA Paul Durrant
2023-11-22 12:25 ` David Woodhouse [this message]
2023-11-22 12:18 ` [PATCH v9 09/15] KVM: xen: allow shared_info to be mapped by fixed HVA Paul Durrant
2023-11-22 12:18 ` [PATCH v9 10/15] KVM: xen: allow vcpu_info " Paul Durrant
2023-11-22 12:18 ` [PATCH v9 11/15] KVM: selftests / xen: map shared_info using HVA rather than GFN Paul Durrant
2023-11-22 12:18 ` [PATCH v9 12/15] KVM: selftests / xen: re-map vcpu_info using HVA rather than GPA Paul Durrant
2023-11-22 12:18 ` [PATCH v9 13/15] KVM: xen: advertize the KVM_XEN_HVM_CONFIG_SHARED_INFO_HVA capability Paul Durrant
2023-11-22 12:18 ` [PATCH v9 14/15] KVM: xen: split up kvm_xen_set_evtchn_fast() Paul Durrant
2023-11-22 12:18 ` [PATCH v9 15/15] KVM: xen: allow vcpu_info content to be 'safely' copied Paul Durrant
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=c7623704c17f3ea2622b700dde525522701c02c7.camel@infradead.org \
--to=dwmw2@infradead.org \
--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=mingo@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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;
as well as URLs for NNTP newsgroup(s).