From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Laurent Vivier" <lvivier@redhat.com>,
"Tyrone Ting" <kfting@nuvoton.com>,
"Bin Meng" <bmeng.cn@gmail.com>, "Hao Wu" <wuhaotsh@google.com>,
"Francisco Iglesias" <francisco.iglesias@amd.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Cédric Le Goater" <clg@kaod.org>,
qemu-arm@nongnu.org, "Joel Stanley" <joel@jms.id.au>,
"Sai Pavan Boddu" <sai.pavan.boddu@amd.com>,
devel@lists.libvirt.org, "Luc Michel" <luc.michel@amd.com>,
"Cédric Le Goater" <clg@redhat.com>
Subject: Re: [PATCH v3 06/17] hw/sd/sdcard: Do not store vendor data on block drive (CMD56)
Date: Tue, 9 Jul 2024 17:01:32 -0400 [thread overview]
Message-ID: <Zo2lLLAwcZ8bBvO2@x1n> (raw)
In-Reply-To: <87cynmfggx.fsf@suse.de>
On Tue, Jul 09, 2024 at 05:38:54PM -0300, Fabiano Rosas wrote:
> Philippe Mathieu-Daudé <philmd@linaro.org> writes:
>
> > "General command" (GEN_CMD, CMD56) is described as:
> >
> > GEN_CMD is the same as the single block read or write
> > commands (CMD24 or CMD17). The difference is that [...]
> > the data block is not a memory payload data but has a
> > vendor specific format and meaning.
> >
> > Thus this block must not be stored overwriting data block
> > on underlying storage drive. Keep it in a dedicated
> > 'vendor_data[]' array.
> >
> > Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> > Tested-by: Cédric Le Goater <clg@redhat.com>
> > ---
> > RFC: Is it safe to reuse VMSTATE_UNUSED_V() (which happens
> > to be the same size)?
>
> Hi, sorry it took some time to get to this, I had just left for vacation
> when you first posted.
And I totally overlooked there's the email.. until you replied. Welcome
back.
>
> I think it's ok:
>
> {
> "field": "unused",
> "version_id": 1,
> "field_exists": false,
> "size": 512
> },
>
> vs.
>
> {
> "field": "vendor_data",
> "version_id": 0,
> "field_exists": false,
> "num": 512,
> "size": 1
> },
>
> The unused field was introduced in 2016 so there's no chance of
> migrating a QEMU that old to/from 9.1.
What happens if an old qemu 9.0 sends rubbish here to a new QEMU, while the
new QEMU would consider it meaningful data?
--
Peter Xu
next prev parent reply other threads:[~2024-07-09 21:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 16:22 [PATCH v3 00/17] hw/sd/sdcard: Accumulation of cleanups and fixes Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 01/17] hw/sd/sdcard: Deprecate support for spec v1.10 Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 02/17] hw/sd/sdcard: Use spec v3.01 by default Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 03/17] hw/sd/sdcard: Track last command used to help logging Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 04/17] hw/sd/sdcard: Trace block offset in READ/WRITE data accesses Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 05/17] hw/sd/sdcard: Trace requested address computed by sd_req_get_address() Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 06/17] hw/sd/sdcard: Do not store vendor data on block drive (CMD56) Philippe Mathieu-Daudé
2024-07-09 20:38 ` Fabiano Rosas
2024-07-09 21:01 ` Peter Xu [this message]
2024-07-10 14:08 ` Fabiano Rosas
2024-07-10 15:01 ` Peter Xu
2024-07-10 16:21 ` Fabiano Rosas
2024-07-10 19:13 ` Peter Xu
2024-07-10 19:48 ` Fabiano Rosas
2024-07-10 20:11 ` Peter Xu
2024-07-10 21:38 ` Fabiano Rosas
2024-07-10 22:06 ` Peter Xu
2024-07-11 13:34 ` Fabiano Rosas
2024-07-11 14:10 ` Peter Xu
2024-07-11 14:44 ` Fabiano Rosas
2024-07-11 14:56 ` Peter Xu
2024-07-11 15:03 ` Fabiano Rosas
2024-06-27 16:22 ` [PATCH v3 07/17] hw/sd/sdcard: Send WRITE_PROT bits MSB first (CMD30) Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 08/17] hw/sd/sdcard: Send NUM_WR_BLOCKS bits MSB first (ACMD22) Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 09/17] hw/sd/sdcard: Use READY_FOR_DATA definition instead of magic value Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 10/17] hw/sd/sdcard: Assign SDCardStates enum values Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 11/17] hw/sd/sdcard: Simplify sd_inactive_state handling Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 12/17] hw/sd/sdcard: Restrict SWITCH_FUNCTION to sd_transfer_state (CMD6) Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 13/17] hw/sd/sdcard: Add direct reference to SDProto in SDState Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 14/17] hw/sd/sdcard: Extract sd_blk_len() helper Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 15/17] tests/qtest: Disable npcm7xx_sdhci tests using hardcoded RCA Philippe Mathieu-Daudé
2024-06-27 16:47 ` Thomas Huth
2024-06-27 17:19 ` Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 16/17] hw/sd/sdcard: Generate random RCA value Philippe Mathieu-Daudé
2024-06-27 16:22 ` [PATCH v3 17/17] hw/sd/sdcard: Introduce definitions for EXT_CSD register Philippe Mathieu-Daudé
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=Zo2lLLAwcZ8bBvO2@x1n \
--to=peterx@redhat.com \
--cc=bmeng.cn@gmail.com \
--cc=clg@kaod.org \
--cc=clg@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=farosas@suse.de \
--cc=francisco.iglesias@amd.com \
--cc=joel@jms.id.au \
--cc=kfting@nuvoton.com \
--cc=luc.michel@amd.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sai.pavan.boddu@amd.com \
--cc=thuth@redhat.com \
--cc=wuhaotsh@google.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).