kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: KVM Man <kvmman602@gmail.com>
To: kvm@vger.kernel.org
Subject: kvm_read_guest_virt returning unexpected data
Date: Wed, 21 Jul 2021 09:20:18 -0500	[thread overview]
Message-ID: <CAN-39qaEWAcKxB6cw64tD14VCDiVHZ9zj43a=j475j+FWVWJeg@mail.gmail.com> (raw)

Hi,

I'm making changes to KVM on linux 5.11.4 while using qemu 5.0.0 and
having issues using kvm_read_guest_virt successfully with an x86_64 VM
guest.

I call kvm_read_guest_virt in a VM exit handler, and it returns data
that's unexpected, as compared to what I see with a kernel debugger
attached to the guest. The function returns a successful error code
(X86EMUL_CONTINUE), and I've verified that virtual to physical address
translation is working properly when kvm_read_guest_virt_helper calls
vcpu->arch.walk_mmu->gva_to_gpa.

Are there any reasons that this function would not work as expected?

Thanks.

                 reply	other threads:[~2021-07-21 14:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAN-39qaEWAcKxB6cw64tD14VCDiVHZ9zj43a=j475j+FWVWJeg@mail.gmail.com' \
    --to=kvmman602@gmail.com \
    --cc=kvm@vger.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).