From: Marc Zyngier <maz@kernel.org>
To: Raghavendra Rao Ananta <rananta@google.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
James Morse <james.morse@arm.com>
Cc: Jing Zhang <jingzhangos@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Reiji Watanabe <reijiw@google.com>,
kvmarm@lists.cs.columbia.edu, Peter Shier <pshier@google.com>,
Oliver Upton <oupton@google.com>,
linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>,
Ricardo Koller <ricarkol@google.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] KVM: arm64: Trim guest debug exception handling
Date: Thu, 26 Aug 2021 11:37:46 +0100 [thread overview]
Message-ID: <162997424183.1640651.9657746284386330796.b4-ty@kernel.org> (raw)
In-Reply-To: <20210823223940.1878930-1-rananta@google.com>
On Mon, 23 Aug 2021 22:39:40 +0000, Raghavendra Rao Ananta wrote:
> The switch-case for handling guest debug exception covers
> all the debug exception classes, but functionally, doesn't
> do anything with them other than ESR_ELx_EC_WATCHPT_LOW.
> Moreover, even though handled well, the 'default' case
> could be confusing from a security point of view, stating
> that the guests' actions can potentially flood the syslog.
> But in reality, the code is unreachable.
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: Trim guest debug exception handling
commit: 8ce8a6fce9bfd3fcabe230ad104e2caf08b2e58d
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2021-08-26 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 22:39 [PATCH] KVM: arm64: Trim guest debug exception handling Raghavendra Rao Ananta
2021-08-26 10:37 ` Marc Zyngier [this message]
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=162997424183.1640651.9657746284386330796.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=jingzhangos@google.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oupton@google.com \
--cc=pshier@google.com \
--cc=rananta@google.com \
--cc=reijiw@google.com \
--cc=ricarkol@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@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).