From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] memory: Provide separate handling of unassigned io ports accesses
Date: Thu, 08 Aug 2013 17:43:06 +0200 [thread overview]
Message-ID: <5203BC8A.8040605@siemens.com> (raw)
In-Reply-To: <CAFEAcA82uA4KON=rXoertgMtL1ZXCpaWFvicZAjB+ZOfG4fK0w@mail.gmail.com>
On 2013-08-08 17:33, Peter Maydell wrote:
> On 3 August 2013 09:31, Jan Kiszka <jan.kiszka@web.de> wrote:
>> --- a/ioport.c
>> +++ b/ioport.c
>> @@ -44,6 +44,22 @@ typedef struct MemoryRegionPortioList {
>> MemoryRegionPortio ports[];
>> } MemoryRegionPortioList;
>>
>> +static uint64_t unassigned_io_read(void *opaque, hwaddr addr, unsigned size)
>> +{
>> + return -1UL;
>
> This should probably be "-1ULL", otherwise we'll return
> different values on 32 bit and 64 bit hosts. (Actually
> managing a 64 bit read of the i/o space is pretty
> unlikely, though possibly alpha memory-mapped via the
> PCI space might let you do it.)
No problem with changing this - but wouldn't 64-bit i/o accesses be a
bug? It's not allowed according to PCI, no device can handle it
(officially), so no arch should forward such requests from mmio, rather
break them up first.
>
> PS: something about the way these patches were submitted
> has confused Anthony's patches tool -- it reports them
> as two separate patches rather than a single series.
> (No cover letter, maybe?)
Something on my side broke the reference from the second to the first email.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-08-08 15:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 8:31 [Qemu-devel] [PATCH 1/2] memory: Provide separate handling of unassigned io ports accesses Jan Kiszka
2013-08-05 9:34 ` Andreas Färber
2013-08-05 9:38 ` Jan Kiszka
2013-08-05 9:59 ` Peter Maydell
2013-08-05 10:29 ` Andreas Färber
2013-08-05 10:30 ` Jan Kiszka
2013-08-05 10:36 ` Peter Maydell
2013-08-05 10:44 ` Jan Kiszka
2013-08-05 10:51 ` Peter Maydell
2013-08-05 11:03 ` Jan Kiszka
2013-08-05 11:35 ` Andreas Färber
2013-08-05 11:38 ` Jan Kiszka
2013-08-05 11:10 ` Paolo Bonzini
2013-08-05 11:07 ` Paolo Bonzini
2013-08-05 20:19 ` Richard Henderson
2013-08-08 15:33 ` Peter Maydell
2013-08-08 15:43 ` Jan Kiszka [this message]
2013-08-09 7:41 ` Paolo Bonzini
2013-08-09 16:49 ` Andreas Färber
2013-08-09 18:48 ` Richard Henderson
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=5203BC8A.8040605@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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.