From: Stefan Weil <sw@weilnetz.de>
To: Daniel Verkamp <daniel@drv.nu>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Anthony Liguori" <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] ahci: SATA FIS is 20 bytes, not 0x20
Date: Wed, 23 May 2012 17:48:29 +0200 [thread overview]
Message-ID: <4FBD06CD.2070304@weilnetz.de> (raw)
In-Reply-To: <1337729202-26850-1-git-send-email-daniel@drv.nu>
Am 23.05.2012 01:26, schrieb Daniel Verkamp:
> As in the SATA and AHCI specifications, a FIS is 5 Dwords of 4 bytes
> each, which comes to 20 bytes (decimal), not 0x20.
>
> Signed-off-by: Daniel Verkamp<daniel@drv.nu>
> ---
> hw/ide/ahci.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/ide/ahci.c b/hw/ide/ahci.c
> index a883a92..2d7d03d 100644
> --- a/hw/ide/ahci.c
> +++ b/hw/ide/ahci.c
> @@ -462,7 +462,7 @@ static void ahci_check_cmd_bh(void *opaque)
>
> static void ahci_init_d2h(AHCIDevice *ad)
> {
> - uint8_t init_fis[0x20];
> + uint8_t init_fis[20];
> IDEState *ide_state =&ad->port.ifs[0];
The current code only uses 14 elements, so 20 elements
still waste some local memory (and 0x20 elements waste
even more).
>
>
> memset(init_fis, 0, sizeof(init_fis));
> @@ -619,7 +619,7 @@ static void ahci_write_fis_d2h(AHCIDevice *ad, uint8_t *cmd_fis)
> d2h_fis[11] = cmd_fis[11];
> d2h_fis[12] = cmd_fis[12];
> d2h_fis[13] = cmd_fis[13];
> - for (i = 14; i< 0x20; i++) {
> + for (i = 14; i< 20; i++) {
> d2h_fis[i] = 0;
> }
I am not sure whether this change is correct.
This code does _not_ access the array which was allocated above:
d2h_fis = &ad->res_fis[RES_FIS_RFIS];
Regards,
Stefan W.
prev parent reply other threads:[~2012-05-23 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 23:26 [Qemu-devel] [PATCH] ahci: SATA FIS is 20 bytes, not 0x20 Daniel Verkamp
2012-05-23 9:13 ` Kevin Wolf
2012-05-23 9:53 ` Alexander Graf
2012-05-23 10:04 ` Kevin Wolf
2012-05-23 15:48 ` Stefan Weil [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=4FBD06CD.2070304@weilnetz.de \
--to=sw@weilnetz.de \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=daniel@drv.nu \
--cc=kwolf@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.