From: Sean Christopherson <seanjc@google.com>
To: Keith Busch <kbusch@meta.com>
Cc: kvm@vger.kernel.org, x86@kernel.org,
Keith Busch <kbusch@kernel.org>,
Alex Williamson <alex.williamson@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Xu Liu <liuxu@meta.com>
Subject: Re: [PATCH RFC] kvm: emulate avx vmovdq
Date: Wed, 21 Aug 2024 09:12:20 -0700 [thread overview]
Message-ID: <ZsYR5BdX0y4gntKx@google.com> (raw)
In-Reply-To: <20240820230431.3850991-1-kbusch@meta.com>
On Tue, Aug 20, 2024, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> Because people would like to use this (see "Link"), interpret the VEX
Please explicitly call define the use case in the changelog. Yeah, I can follow
the link, but I shouldn't have to just to understand that this is the compiler
generating vmovdqu for its built-in memcpy().
> prefix and emulate mov instrutions accordingly. The only avx
> instructions emulated here are the aligned and unaligned mov.
> Everything else will fail as before.
>
> This is new territory for me, so any feedback is appreciated.
Heh, this is probably new territory for everyone except possibly Paolo. I don't
recall the last time KVM was effectively forced to add emulation for something
this gnarly.
next prev parent reply other threads:[~2024-08-21 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 23:04 [PATCH RFC] kvm: emulate avx vmovdq Keith Busch
2024-08-21 16:12 ` Sean Christopherson [this message]
2024-08-21 16:34 ` Keith Busch
2024-08-22 7:22 ` Tao Su
2024-08-22 14:39 ` Keith Busch
2024-08-23 3:47 ` Tao Su
2024-09-03 21:25 ` Keith Busch
2024-09-22 12:57 ` Sean Christopherson
2024-09-25 8:09 ` Keith Busch
2024-09-25 13:46 ` Sean Christopherson
2025-11-04 17:40 ` Paolo Bonzini
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=ZsYR5BdX0y4gntKx@google.com \
--to=seanjc@google.com \
--cc=alex.williamson@redhat.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=kvm@vger.kernel.org \
--cc=liuxu@meta.com \
--cc=pbonzini@redhat.com \
--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 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.