From: Zenghui Yu <yuzenghui@huawei.com>
To: <kvmarm@lists.cs.columbia.edu>, <linux-arm-kernel@lists.infradead.org>
Cc: marc.zyngier@arm.com
Subject: KVM: arm64: Update kvm_arm_exception_class and esr_class_str for new EC
Date: Fri, 12 Jul 2019 15:12:31 +0800 [thread overview]
Message-ID: <e6e8cd90-d309-7f1a-c8d1-85aa03fe0dfb@huawei.com> (raw)
Hi,
I noticed that we've added two ESR exception classes for new hardware
extensions - ESR_ELx_EC_SVE and ESR_ELx_EC_PAC. Should we also update
"kvm_arm_exception_class" and "esr_class_str" for these two EC, which
might be useful for debug in the future?
Thanks,
zenghui
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next reply other threads:[~2019-07-12 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 7:12 Zenghui Yu [this message]
2019-07-12 8:03 ` KVM: arm64: Update kvm_arm_exception_class and esr_class_str for new EC Marc Zyngier
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=e6e8cd90-d309-7f1a-c8d1-85aa03fe0dfb@huawei.com \
--to=yuzenghui@huawei.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.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).