From: Ashish Kalra <ashish.kalra@amd.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: thomas.lendacky@amd.com, jon.grimm@amd.com,
brijesh.singh@amd.com, dgilbert@redhat.com,
qemu-devel@nongnu.org
Subject: Re: SEV guest debugging support for Qemu
Date: Fri, 25 Sep 2020 23:48:41 +0000 [thread overview]
Message-ID: <20200925234841.GA11103@ashkalra_ubuntu_server> (raw)
In-Reply-To: <e9b09c9b-4d4c-c6de-4cce-807effc38836@redhat.com>
Hello Paolo,
On Fri, Sep 25, 2020 at 10:56:10PM +0200, Paolo Bonzini wrote:
> On 25/09/20 22:46, Ashish Kalra wrote:
> > I was also considering abstracting this vendor/SEV specific debug
> > interface via the CPUClass object, the CPUClass object aleady has cpu
> > specific methods for doing things like guest VA to GPA translations like the
> > get_phys_page_attrs_debug() method and it will be a simple and clean
> > approach to override this method with a SEV specific
> > get_phys_page_attrs_debug() if SEV guest is active and SEV debug policy
> > is allowed. [...]
> >
> > I can probably add new interfaces/methods to this CPUClass object for
> > guest memory read/writes for debugging purpose and then invoke the same
> > from the generic cpu_memory_rw_debug() interface.
> >
> > Let me know your thougts on abstracting this debug interface via the
> > CPUClass object ?
> >
> > Or the other option is to introduce the new MemoryDebugOps you described
> > above and additionally apply SEV/SEV-ES considerations in CPUClass
> > methods such as gdb_read_register, gdb_write_register, etc.
>
> Yes, this makes the most sense, however you're right that you don't need
> translate in MemoryDebugOps. I don't think read/write should be moved
> to CPUClass, however, since you can use a MemTxAttr to tell the
> read/write MemoryDebugOps whether the page is encrypted or not.
>
Thanks for your input, i have one additional query with reference to this support :
For all explicitly unecrypted guest memory regions such as S/W IOTLB bounce buffers,
dma_decrypted() allocated regions and for guest regions marked as "__bss_decrypted",
we need to ensure that DBG_DECRYPT API calls are bypassed for such
regions and those regions are dumped as un-encrypted.
This guest memory regions encryption status is found using KVM's page encryption bitmap
support which is part of the page encryption bitmap hypercall interface of the
KVM/QEMU SEV live migration patches.
As this additional debug support is dependent on the KVM's page encryption bitmap
support, are there any updates on KVM SEV live migration patches ?
Thanks,
Ashish
next prev parent reply other threads:[~2020-09-25 23:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 20:11 SEV guest debugging support for Qemu Ashish Kalra
2020-09-24 13:53 ` Dr. David Alan Gilbert
2020-09-24 19:06 ` Ashish Kalra
2020-09-24 19:37 ` Brijesh Singh
2020-09-24 21:52 ` Ashish Kalra
2020-09-25 8:39 ` Dr. David Alan Gilbert
2020-09-25 8:51 ` Paolo Bonzini
2020-09-25 20:46 ` Ashish Kalra
2020-09-25 20:56 ` Paolo Bonzini
2020-09-25 23:48 ` Ashish Kalra [this message]
2020-09-26 0:02 ` Paolo Bonzini
2020-09-28 13:26 ` Ashish Kalra
2020-09-28 18:08 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2020-09-22 19:45 Kalra, Ashish
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=20200925234841.GA11103@ashkalra_ubuntu_server \
--to=ashish.kalra@amd.com \
--cc=brijesh.singh@amd.com \
--cc=dgilbert@redhat.com \
--cc=jon.grimm@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.lendacky@amd.com \
/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).