From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 10/10] Compile virtio-blk only once
Date: Fri, 26 Mar 2010 15:33:17 -0500 [thread overview]
Message-ID: <4BAD1A0D.5030101@codemonkey.ws> (raw)
In-Reply-To: <f43fc5581003261204i596f1f95qfb70129e58800cdf@mail.gmail.com>
On 03/26/2010 02:04 PM, Blue Swirl wrote:
> Replace access macros with direct accesses.
>
> Signed-off-by: Blue Swirl<blauwirbel@gmail.com>
> ---
> Makefile.objs | 3 ++-
> Makefile.target | 2 +-
> hw/virtio-blk.c | 6 +++---
> 3 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/Makefile.objs b/Makefile.objs
> index cad6490..5612ec2 100644
> --- a/Makefile.objs
> +++ b/Makefile.objs
> @@ -128,7 +128,8 @@ user-obj-y += cutils.o cache-utils.o
>
> hw-obj-y =
> hw-obj-y += loader.o
> -hw-obj-y += virtio.o virtio-console.o virtio-pci.o virtio-net.o
> virtio-serial-bus.o
> +hw-obj-y += virtio.o virtio-console.o virtio-pci.o
> +hw-obj-y += virtio-blk.o virtio-net.o virtio-serial-bus.o
> hw-obj-y += fw_cfg.o pci.o pci_host.o pcie_host.o
> hw-obj-y += watchdog.o
> hw-obj-$(CONFIG_ISA_MMIO) += isa_mmio.o
> diff --git a/Makefile.target b/Makefile.target
> index e43e138..169c11e 100644
> --- a/Makefile.target
> +++ b/Makefile.target
> @@ -165,7 +165,7 @@ obj-y = vl.o monitor.o machine.o gdbstub.o
> obj-y += qemu-timer.o
> # virtio has to be here due to weird dependency between PCI and virtio-net.
> # need to fix this properly
> -obj-y += virtio-blk.o virtio-balloon.o
> +obj-y += virtio-balloon.o
> obj-y += rwhandler.o
> obj-$(CONFIG_KVM) += kvm.o kvm-all.o
> LIBS+=-lz
> diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
> index 9915840..d9dd9a7 100644
> --- a/hw/virtio-blk.c
> +++ b/hw/virtio-blk.c
> @@ -411,9 +411,9 @@ static void virtio_blk_update_config(VirtIODevice
> *vdev, uint8_t *config)
> bdrv_get_geometry(s->bs,&capacity);
> bdrv_get_geometry_hint(s->bs,&cylinders,&heads,&secs);
> memset(&blkcfg, 0, sizeof(blkcfg));
> - stq_raw(&blkcfg.capacity, capacity);
> - stl_raw(&blkcfg.seg_max, 128 - 2);
> - stw_raw(&blkcfg.cylinders, cylinders);
> + blkcfg.capacity = capacity;
> + blkcfg.seg_max = 128 - 2;
> + blkcfg.cylinders = cylinders;
>
This looks wrong to me.
These values need to be in guest endianness.
Regards,
Anthony Liguori
> blkcfg.heads = heads;
> blkcfg.sectors = secs& ~s->sector_mask;
> blkcfg.blk_size = s->conf->logical_block_size;
>
next prev parent reply other threads:[~2010-03-26 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 19:04 [Qemu-devel] [PATCH 10/10] Compile virtio-blk only once Blue Swirl
2010-03-26 20:33 ` Anthony Liguori [this message]
2010-03-26 21:35 ` Blue Swirl
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=4BAD1A0D.5030101@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.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.