From: P J P <ppandit@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Fakhri Zulkifli <mohdfakhrizulkifli@gmail.com>,
Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] sun4u: add power_mem_read routine
Date: Fri, 4 Jan 2019 11:17:54 +0530 (IST) [thread overview]
Message-ID: <nycvar.YSQ.7.76.1901041111410.31402@xnncv> (raw)
In-Reply-To: <cd325b25-15ee-46e4-896e-e5904340b1bf@ilande.co.uk>
Hello Mark,
+-- On Thu, 3 Jan 2019, Mark Cave-Ayland wrote --+
| > /* Power */
| > +static uint64_t power_mem_read(void *opaque, hwaddr addr, unsigned size)
| > +{
| > + return 0xffffffff;
| > +}
| > +
| >
| > static const MemoryRegionOps power_mem_ops = {
| > + .read = power_mem_read,
| > .write = power_mem_write,
| > .endianness = DEVICE_NATIVE_ENDIAN,
| > .valid = {
|
| Certainly the addition of the missing read function is valid, although I see that
| you've defaulted reads to returning 0xffffffff - can you point me towards the source
| that indicates that this behaviour matches that of real Ultra-5 hardware?
-> https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg02787.html
I haven't checked Ultra-5 h/w spec, return value was chosen similar to above
one, thinking unimplemented .read need not return success.
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2019-01-04 5:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 9:37 [Qemu-devel] [PATCH] sun4u: add power_mem_read routine P J P
2019-01-03 12:33 ` Mark Cave-Ayland
2019-01-04 5:47 ` P J P [this message]
2019-01-04 8:24 ` Mark Cave-Ayland
2019-01-04 9:53 ` P J P
2019-01-04 10:37 ` Philippe Mathieu-Daudé
2019-01-07 12:59 ` Mark Cave-Ayland
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=nycvar.YSQ.7.76.1901041111410.31402@xnncv \
--to=ppandit@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mohdfakhrizulkifli@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).