From: Fabien Chouteau <chouteau@adacore.com>
To: Avi Kivity <avi@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-devel@nongnu.org, atar4qemu@gmail.com
Subject: Re: [Qemu-devel] [PATCH] memory: fix return value on unassigned reads
Date: Thu, 26 Jan 2012 12:31:37 +0100 [thread overview]
Message-ID: <4F213999.4060509@adacore.com> (raw)
In-Reply-To: <1327570411-20432-1-git-send-email-avi@redhat.com>
On 26/01/2012 10:33, Avi Kivity wrote:
> The memory API returns -1 on unassigned reads, different from the original
> in exec.c, which returned zero.
Isn't this return value platform specific?
> This breaks grlib_uart; apparently some users depend on it.
>
> Fix by returning zero; however if reading from the uart is legal, then
> it should be modified to accept reads.
>
That's right, grlib_uart depends on it because I took the easy (lazy?)
way. I will send a patch to handle reads to UART's registers.
--
Fabien Chouteau
next prev parent reply other threads:[~2012-01-26 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 9:33 [Qemu-devel] [PATCH] memory: fix return value on unassigned reads Avi Kivity
2012-01-26 11:31 ` Fabien Chouteau [this message]
2012-01-26 12:18 ` Avi Kivity
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=4F213999.4060509@adacore.com \
--to=chouteau@adacore.com \
--cc=atar4qemu@gmail.com \
--cc=avi@redhat.com \
--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 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).