From: Hannes Reinecke <hare@suse.de>
To: "Salva Peiró" <speirofr@gmail.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] megasas: Add write function to handle write access to PCI BAR 3
Date: Mon, 27 Jul 2015 10:57:17 +0200 [thread overview]
Message-ID: <55B5F26D.1050005@suse.de> (raw)
In-Reply-To: <1437987112-24744-1-git-send-email-speirofr@gmail.com>
On 07/27/2015 10:51 AM, Salva Peiró wrote:
> This patch fixes a QEMU SEGFAULT when a write operation is performed on
> the memory region of the PCI BAR 3 (base address space).
> When a writeb(0xe0000000) is performed the .write function is invoked to
> handle the write access, however, since the .write is not initialised,
> the call to 0, causes QEMU to SEGFAULT.
>
> Signed-off-by: Salva Peiró <speirofr@gmail.com>
> ---
> hw/scsi/megasas.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/hw/scsi/megasas.c b/hw/scsi/megasas.c
> index 51ba9e0..a04369c 100644
> --- a/hw/scsi/megasas.c
> +++ b/hw/scsi/megasas.c
> @@ -2202,8 +2202,15 @@ static uint64_t megasas_queue_read(void *opaque, hwaddr addr,
> return 0;
> }
>
> +static void megasas_queue_write(void *opaque, hwaddr addr,
> + uint64_t val, unsigned size)
> +{
> + return;
> +}
> +
> static const MemoryRegionOps megasas_queue_ops = {
> .read = megasas_queue_read,
> + .write = megasas_queue_write,
> .endianness = DEVICE_LITTLE_ENDIAN,
> .impl = {
> .min_access_size = 8,
>
Yep, that's the correct fix.
Acked-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-07-27 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 8:51 [Qemu-devel] [PATCH] megasas: Add write function to handle write access to PCI BAR 3 Salva Peiró
2015-07-27 8:57 ` Hannes Reinecke [this message]
2015-07-27 10:21 ` Paolo Bonzini
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=55B5F26D.1050005@suse.de \
--to=hare@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=speirofr@gmail.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 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.