From: John Snow <jsnow@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Bin Meng <bin.meng@windriver.com>,
qemu-block@nongnu.org, Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [PATCH] hw/sd/sdhci: Report error when guest access protected registers
Date: Thu, 4 Mar 2021 18:37:27 -0500 [thread overview]
Message-ID: <fdac84ee-8c86-036b-1db5-a174cb8f530c@redhat.com> (raw)
In-Reply-To: <20210218175648.1636219-1-f4bug@amsat.org>
On 2/18/21 12:56 PM, Philippe Mathieu-Daudé wrote:
> The SDHC_SYSAD and SDHC_BLKSIZE can not be accessed while a
> transaction is in progress, see 'SD Host Controller Simplified
> Specification'
>
> 1.5) SD Command Generation
>
> The Host Driver should not read the SDMA System Address, Block
> Size and Block Count registers during a data transaction unless
> the transfer is stopped because the value is changing and not
> stable.
>
Naive question: Is this an RFC2119 "SHOULD NOT"? (i.e., does it have a
defined behavior that you are simply encouraged to avoid?)
Is it really an error?
> Report guest intents as errors.
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> Based-on: <1613447214-81951-1-git-send-email-bmeng.cn@gmail.com>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> hw/sd/sdhci.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/hw/sd/sdhci.c b/hw/sd/sdhci.c
> index 5b8678110b0..98928c18542 100644
> --- a/hw/sd/sdhci.c
> +++ b/hw/sd/sdhci.c
> @@ -1136,6 +1136,10 @@ sdhci_write(void *opaque, hwaddr offset, uint64_t val, unsigned size)
> sdhci_sdma_transfer_single_block(s);
> }
> }
> + } else {
> + qemu_log_mask(LOG_GUEST_ERROR,
> + "%s: Transfer already in progress,"
> + " can not update SYSAD", __func__);
> }
> break;
> case SDHC_BLKSIZE:
> @@ -1163,8 +1167,11 @@ sdhci_write(void *opaque, hwaddr offset, uint64_t val, unsigned size)
> if (blksize != s->blksize) {
> s->data_count = 0;
> }
> + } else {
> + qemu_log_mask(LOG_GUEST_ERROR,
> + "%s: Transfer already in progress,"
> + " can not update BLKSIZE", __func__);
> }
> -
> break;
> case SDHC_ARGUMENT:
> MASKED_WRITE(s->argument, mask, value);
>
next prev parent reply other threads:[~2021-03-04 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 17:56 [PATCH] hw/sd/sdhci: Report error when guest access protected registers Philippe Mathieu-Daudé
2021-03-04 23:37 ` John Snow [this message]
2021-03-05 2:26 ` Bin Meng
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=fdac84ee-8c86-036b-1db5-a174cb8f530c@redhat.com \
--to=jsnow@redhat.com \
--cc=bin.meng@windriver.com \
--cc=bmeng.cn@gmail.com \
--cc=f4bug@amsat.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).