From: Paolo Bonzini <pbonzini@redhat.com>
To: Ashish Kalra <ashish.kalra@amd.com>,
dgilbert@redhat.com, qemu-devel@nongnu.org
Cc: thomas.lendacky@amd.com, jon.grimm@amd.com, brijesh.singh@amd.com
Subject: Re: SEV guest debugging support for Qemu
Date: Fri, 25 Sep 2020 10:51:05 +0200 [thread overview]
Message-ID: <5a58509c-5838-f0aa-d9ab-4f85ca0ac35f@redhat.com> (raw)
In-Reply-To: <20200922201124.GA6606@ashkalra_ubuntu_server>
On 22/09/20 22:11, Ashish Kalra wrote:
> This internally invokes the address_space_rw() accessor functions
> which we had "fixed" internally (as part of the earlier patch) to
> invoke memory region specific debug ops. In our earlier approach we
> were adding debug ops/callbacks to memory regions and as per comments
> on our earlier patches, Paolo was not happy with this debug API for
> MemoryRegions and hence the SEV support for Qemu was merged without
> the debug support.
My complaint was only about hooking into address_space_read and
address_space_write; I think the hook should not touch general-purpose
(non-debug) code if possible, so something like this:
typedef struct MemoryDebugOps {
hwaddr (*translate)(CPUState *cpu, target_ulong addr,
MemTxAttrs *attrs);
MemTxResult (*read)(AddressSpace *as, hwaddr phys_addr,
MemTxAttrs attrs, void *buf,
hwaddr len);
MemTxResult (*write)(AddressSpace *as, hwaddr phys_addr,
MemTxAttrs attrs, const void *buf,
hwaddr len);
} MemoryDebugOps;
These ops would be used only by cpu_memory_rw_debug and would default to
static const MemoryDebugOps default_debug_ops = {
.translate = cpu_get_phys_page_attrs_debug,
.read = address_space_read,
.write = address_space_write_rom
};
static const MemoryDebugOps *debug_ops = &default_debug_ops;
Paolo
next prev parent reply other threads:[~2020-09-25 8:53 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 [this message]
2020-09-25 20:46 ` Ashish Kalra
2020-09-25 20:56 ` Paolo Bonzini
2020-09-25 23:48 ` Ashish Kalra
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=5a58509c-5838-f0aa-d9ab-4f85ca0ac35f@redhat.com \
--to=pbonzini@redhat.com \
--cc=ashish.kalra@amd.com \
--cc=brijesh.singh@amd.com \
--cc=dgilbert@redhat.com \
--cc=jon.grimm@amd.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).